Featured Skills

Analyze staged changes and write a precise Conventional Commit message — type, scope, summary, and body from the actual diff.

Use when: Before every meaningful commit. Stops you from writing "fix stuff" forever.

Generate a complete pull request title, summary, motivation, implementation notes, and testing checklist from the branch diff.

Use when: Immediately after finishing a feature. Writes the PR body you always skip.

Fix a specific bug, error, or failing test with the minimal change needed. Identifies root cause before writing any code.

Use when: Paste an error message or describe the bug. Gets a precise fix, not a rewrite.

Perform a thorough code review — correctness, security, performance, readability — with severity-rated findings and specific fixes.

Use when: Before merging any PR. Catches what human reviewers miss when they're tired.

Write comprehensive tests for any function, class, or module — happy paths, edge cases, error states, and mocks.

Use when: After writing new code or when coverage is low. Works with any test framework.

Break down any feature request or task into a step-by-step implementation plan before writing a single line of code.

Use when: Before starting any non-trivial feature. Align on the approach before you're 3 hours deep.

Document the current session's progress, open questions, next steps, and context — so any agent or human can continue seamlessly.

Use when: End of a work session, or when switching between AI agents and humans.

Run lint, tests, and build — then automatically diagnose and fix any failures, repeat up to 3 times until everything is green.

Use when: After making changes, to ensure nothing is broken before committing.

Deep security audit covering OWASP Top 10, secrets exposure, insecure dependencies, and auth/authz flaws — with prioritized fixes.

Use when: Before any production deployment, open-source release, or security-sensitive feature.

Reduce complexity, eliminate duplication, improve naming, and remove dead code — without changing behavior.

Use when: After a feature is working and you want to clean it up before the PR.

Pre-deployment checklist — runs tests, checks for secrets, validates env config, confirms migration state, and generates a deployment summary.

Use when: Before every production push. Makes sure you haven't forgotten anything.

Generate a complete CI/CD pipeline — lint, typecheck, test, build, and deploy stages — for GitHub Actions, GitLab CI, or CircleCI.

Use when: New project or existing project with no CI. Get full pipeline in 2 minutes.

Generate an optimized, production-ready Dockerfile — multi-stage build, minimal image, non-root user, and .dockerignore.

Use when: Containerizing a project for the first time, or improving an existing image.

Generate or update documentation — JSDoc/TSDoc inline comments, README, or API reference — for any file or whole project.

Use when: After writing code, or when onboarding new contributors who say "where are the docs?"

Generate a daily standup from git activity — what you did yesterday, what's in progress, and any blockers.

Use when: Every morning before standup. Turns git history into human-readable progress.

Scaffold a complete MCP server from scratch — tool definitions, handlers, auth, error handling, and Claude Desktop config.

Use when: Starting a new MCP server integration for any API or data source.

Diagnose MCP connection and tool call failures — transport, handshake, capability negotiation, and response format errors.

Use when: When your MCP server connects but tools fail, or the client can't connect at all.