khasky

Safely upgrades dependencies and reviews breaking changes. Use when updating packages, resolving vulnerabilities, or when the user asks to bump or upgrade dependencies.

Creates and updates READMEs, API documentation, runbooks, and in-code documentation for any project type or audience. Use when documenting a project, API, or process, or when documentation is requested.

Breaks large tasks or epics into subtasks with acceptance criteria and dependencies. Use when planning work, creating tickets, or when the user asks to break down a task. Applies to any project or team size.

Applies structured logging, levels, and PII handling. Use when adding or reviewing logs, or when the user asks for logging standards.

Audits and suggests fixes for accessibility (WCAG, keyboard, screen readers). Use when checking a11y, before release, or when the user asks for accessibility review.

Generates changelogs and release notes from commits and tags. Use when releasing a version, writing release notes, or maintaining a CHANGELOG.

Requires running verification commands and confirming output before claiming work is complete, fixed, or passing. Apply this before committing, creating PRs, or marking any task done, regardless of language, test runner, or build system.

Maps and navigates unfamiliar codebases quickly. Use when onboarding to a repo, finding where a feature lives, or when the user asks how the codebase is structured.

Reviews code for correctness, security, and team standards, useful for pull requests, diffs, or user-requested code reviews across any language or project.

Universal coding standards, naming, structure, and patterns for consistent code. Use when starting a project, refactoring, setting up lint/format, or enforcing conventions.

Generates conventional commit messages from git diffs. Use when writing commit messages, summarizing staged changes, or when the user mentions commits or changelog.

Deployment strategies, release safety, health checks, and rollback. Use when designing or documenting deploy/rollback, CI/CD, or production readiness. Applies to any stack or platform.

Audits code for common vulnerabilities: injection, secrets, auth, and dependency CVEs. Use when reviewing security, before release, or when the user asks for a security check.

Writes tests before implementation using red-green-refactor. Use when implementing features or bugfixes, or when the user asks for TDD.

Documents and maintains environment variables and config (e.g. .env.example). Use when setting up config, onboarding, or when the user asks for env docs or .env.example.

Refactors code in small, test-backed steps without changing behavior. Use when refactoring, improving structure, or when the user asks to refactor safely.

Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments. Use when creating or altering tables, columns, indexes, or planning schema changes.

REST API design patterns cover resource naming, status codes, pagination, filtering, errors, versioning, and rate limiting. Apply these patterns when designing or reviewing APIs.

Applies branch naming, merge strategy, and cleanup conventions. Use when creating branches, merging, or when the user asks about git workflow or branch strategy.

Debugs by reproducing, isolating root cause, then fixing. Use when fixing bugs, investigating failures, or when the user reports an error or unexpected behavior. Applies to any language, runtime, or system.

Creates and maintains OpenAPI (Swagger) specs from code or design. Use when documenting APIs, generating client/server stubs, or when the user asks for OpenAPI or Swagger.

Applies consistent error handling, logging, and user-facing messages. Use when adding or refactoring error handling, or when the user asks for error handling patterns.

Respond to code review feedback by verifying before implementing, clarifying unclear items, and pushing back with technical reasoning when needed. This applies to any team or culture when receiving PR feedback or review comments.

Creates and updates runbooks and incident response steps. Use when documenting ops procedures, incident response, or when the user asks for a runbook.

Generates pull request title and description from branch name and diff. Use when opening a PR, drafting PR text, or when the user asks for a PR description.