Instrument code with structured logging or tracing to diagnose a runtime issue — spans around suspect calls, correlation IDs, timing, and key state at boundaries. Use when a bug only reproduces at runtime and the cause is unclear, when diagnosing why…
Generate reference documentation for a project's public API or HTTP endpoints directly from the source — signatures, parameters, return values, status codes, and examples. Use when the user says "document the API", "write API docs", "document these…
Generate or update a CHANGELOG entry from git history since the last release, grouped by change type. Use when the user says "update the changelog", "add a changelog entry", "generate release notes", or is cutting a release and needs the CHANGELOG filled in.
Review a code diff or pull request for correctness, security, and style, reporting findings ranked by severity with concrete failure scenarios and fixes. Use when the user says "review this", "code review", "look over my PR", or asks to check a diff before…
Create well-formed git commits with clear, conventional messages from the current changes. Use when the user says "commit", "commit this", "make a commit", or asks to save/record staged or unstaged changes to git.
Write a correct, minimal multi-stage Dockerfile and matching .dockerignore for the project. Use when the user asks to dockerize, containerize, or add a Dockerfile to an app.
Map an unfamiliar repository from the ground up — locate entry points, reconstruct the architecture, and trace how data flows through the layers. Use when the user says "explain this codebase", "how does this project work", "give me an overview", "where do I…
Find the exact commit that introduced a bug or regression using git bisect, automated with a test command when possible. Use when the user says "find the commit that broke X", "this used to work", "bisect this regression", or wants to pinpoint when a bug was…