Review Implementation

Use this skill to verify and review repository changes before they are described as complete. Discover the project's own checks from its manifests, scripts, docs, CI config, and conversation context instead of assuming a specific package manager, framework, or command shape.

Workflow

1. Build context
   • Read repository instructions such as AGENTS.md, README, docs linked from those files, and relevant area-specific guidance.
   • Resolve the intended base from explicit user or downstream-workflow context, an existing PR base, an explicitly established parent integration branch, or the repository's discovered default branch for ordinary work. Do not hardcode a base branch or guess when these signals conflict.
   • Ensure the base ref is available and sufficiently current to support the review. If the intended base cannot be resolved or inspected, mark the review blocked.
   • Inspect the complete committed branch diff against the intended base using merge-base semantics, such as <base>...HEAD.
   • Inspect local changes in addition to the committed branch diff: staged, unstaged, and untracked files. Do not rely on a working-tree-only diff because it omits committed implementation work.
   • Inspect the commit list and diff statistics for the same range to detect unexpected scope or missing changes.
   • Inspect changed files directly when the diff alone is not enough to understand behavior.
   • If the touched area has a matching local skill or project rule, use it before judging that area.