skills.rest
JBonfim
JBonfimCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

cy-impl-peer-review

Performs Git diff peer reviews with Claude Opus and outputs structured JSON findings.

Updated May 15, 2026
Search Tags:#code review#dev workflow#git diff#implementation verification#cross-LLM#opinionated remediation#artifact reporting
One-click install
npx skills add https://github.com/JBonfim/skill-developer --skill cy-impl-peer-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cy-impl-peer-review
Source: https://github.com/JBonfim/skill-developer/tree/main/.agents/skills/cy-impl-peer-review
Command: npx skills add https://github.com/JBonfim/skill-developer --skill cy-impl-peer-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Prevents shipping an implementation that’s likely to have correctness, security, or integration regressions by running an explicit cross-LLM peer review on the actual diff after an implementation pass.

Core Features & Use Cases

  • Diff-scoped peer review: Reviews either the full base...HEAD change set or a user-specified --files subset to keep feedback relevant.
  • Readiness-gated execution: Runs only when build/tests, diff non-emptiness, and other readiness markers are satisfied, aborting early when the change is not reviewable.
  • Structured remediation workflow: Produces JSON findings (blockers/risks/nits/verdict), then applies only user-selected items after confirmation—without committing, pushing, or auto-looping.

Quick Start

Ask for an Opus implementation peer review after your implementation pass (for example: review the current diff against main and write artifacts under the default peer-reviews folder).

Frequently Asked Questions about cy-impl-peer-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an automated peer review on my git diff before committing?▼

Cross-LLM peer review pressure-tests your git diff using Claude Opus, enforcing diff scoping via --files or --base/--context, and packaging structured findings into JSON output for user-directed remediation.

What is cross-LLM implementation verification for code changes?▼

Cross-LLM implementation verification is an explicit external review of your current diff that prevents shipping correctness, security, or integration regressions by pressure-testing changes before commit.

Can I scope the code review to specific files in my git diff?▼

Yes, you can scope the code review to a specific --files subset or review the full base...HEAD change set to keep peer review feedback relevant to your targeted implementation changes.

Does the peer review automatically apply code fixes to my repository?▼

No, the peer review produces JSON findings and applies only user-selected remediation items after confirmation, without committing, pushing, or auto-looping changes into your repository.

When should I request an implementation peer review in my dev workflow?▼

Request an implementation peer review after an implementation pass for a feature, bug fix, or refactor session when an explicit external review of the current diff is needed before commit or PR submission.

What readiness conditions are required before running a diff review?▼

Diff review execution is readiness-gated and runs only when build/tests, diff non-emptiness, and other readiness markers are satisfied, aborting early when the change is not reviewable.

Related Skills

Explore More Software Engineering Skills→
tomoasleeptomoasleep
2

self-review

Inspect diffs, base branches, and review threads to validate PR quality standards.

Community
Advanced
mkikenmkiken
1

pr-comment-post

Automate posting selected PR review findings as GitHub inline comments with user confirmation.

Community
Intermediate
compozycompozy
96

spec-peer-review

Facilitate cross-LLM peer reviews of code specifications with a specified model.

Official
Advanced
wilsonfaustinowilsonfaustino
2

post-review

Triage and post PR review comments as pending GitHub reviews.

Community
Advanced