Audits a code diff against its specification and project standards, producing severity-labeled findings and a verdict.
npx skills add https://github.com/kieranpotts/skills --skill review-kieranpotts
Please help me install this Agent Skill. Skill: review Source: https://github.com/kieranpotts/skills/tree/main/skills/review Command: npx skills add https://github.com/kieranpotts/skills --skill review-kieranpotts
git diff <base>...HEAD), never edits code or configuration, and suits CI or away-from-keyboard workflows. - Use Case: Before pushing a feature branch, ask the agent to review your diff against the issue's acceptance criteria; it returns file-and-line findings grouped by Specification and Standards axes, plus a merge verdict. ## Quick Start Review this branch against main and check it against the acceptance criteria in the linked issue.High-intent search queries and answers about installing and using this skill.
Read the PR description and linked issue first to extract the acceptance criteria, then pin a comparison base and read the diff commit by commit. Check each criterion explicitly and quote the specification line for every specification finding.
Run the full review procedure over your own diff as though it were a stranger's: pin the base with git diff <base>...HEAD, check correctness, tests, and security, then classify findings by severity. Most easy findings surface in self-review before anyone else looks.
Use four labels: Blocking for issues that gate the merge (correctness, security, untested behavior), Suggestion for improvements acceptable as-is, Nit for optional stylistic points, and Praise to reinforce good patterns. Every comment should carry one label so authors know what blocks the merge.
Yes, this review workflow runs non-interactively and suits continuous integration. The agent determines parameters from context and environment, only asking where specification or standards artifacts live if nothing settles their location.
Request changes when at least one Blocking finding stands, such as a correctness defect, security issue, or new behavior with no test. Approve when nothing blocks, even if Suggestions or Nits remain, since perfection should not hold up delivery.
Review effectiveness drops sharply past a few hundred changed lines because reviewers skim and miss issues. For oversized changes, stop and ask the author to split the work into smaller commits rather than attempting a full review.
otomattyCreate and update GitHub pull requests with automated checks and template descriptions.
mkalkereClaim GitHub PR tasks, address comments, and request re-review.
Amfsa-techIdentify bugs, unsafe logic, and architectural smells in codebases.
HouseGarofaloActivate collaborative pair programming with structured Driver/Navigator and Ping-Pong TDD formats.