dev-review

Runs dual engineering and QA review passes over a change scope and synthesizes findings into analysis.md.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/GinoCanessa/dotnet-fhir-packages --skill dev-review-ginocanessa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-review
Source: https://github.com/GinoCanessa/dotnet-fhir-packages/tree/main/.github/skills/dev-review
Command: npx skills add https://github.com/GinoCanessa/dotnet-fhir-packages --skill dev-review-ginocanessa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Pre-PR code review often misses issues because a single reviewer cannot simultaneously hold an engineering-quality lens and a QA/test-coverage lens. This Skill runs two independent review passes over a defined change scope and merges them into one ranked, actionable analysis report. ## Core Features & Use Cases - Two-track review: A staff-level Engineering Lead pass (antipatterns, hot paths, consistency, dead code, provenance via git history) and a QA Lead pass (coverage, edge cases, regression risk, verifiability) run independently, then a synthesizer deduplicates, ranks by severity, and scores confidence 0-100. - Flexible scope resolution: Review the working tree, last commit, unpushed commits, a commit range, a file list, or the commits recorded in a sibling plan.md slot. - Read-only guarantee: Never modifies source, never commits, never pushes; the only file written is analysis.md under a gitignored scratch/ directory. - Use Case: After finishing a feature branch, run the review on your unpushed commits to get a severity-ranked findings report with file/line citations and concrete recommendations before opening the PR. ## Quick Start Review my unpushed commits with the dev-review skill and write the findings to slot 2.

Frequently Asked Questions about dev-review

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

FAQPage Schema
How do I run a code review on uncommitted changes before a PR?

Invoke the review with the working-tree scope to analyze staged and unstaged changes versus HEAD. The skill runs engineering and QA passes over the diff and writes a severity-ranked analysis.md with cited findings and recommendations.

How to review only the commits not yet pushed to the remote branch?

Use the since-push scope, which resolves to commits ahead of the upstream branch (or the default branch if no upstream is configured). The skill echoes the concrete commit and file list before starting the review passes.

Does the review skill modify my source code or create commits?

No. The skill is strictly read-only with respect to the codebase: it never edits source, stages, commits, or pushes. The only file it writes is the analysis.md report inside the gitignored scratch directory.

What happens when the review scope is very small or very large?

Scopes under 5 changed files and 200 changed lines dispatch a single reviewer sub-agent running both passes sequentially. Larger scopes fan out to parallel engineering and QA sub-agents, capped by the max_subagents setting (default 3, maximum 8).

How are review findings ranked and filtered for noise?

Findings are ranked Blocker through Nit with an independent 0-100 confidence score. Findings below 50 confidence are excluded from numbering, and Blocker or High findings require confidence of 75 or more, with demotion applied otherwise.