review-branch

Reviews branch changes against a diff base and saves a scored review artifact.

1|1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/williamthorsen/codeassembly --skill review-branch-williamthorsen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-branch
Source: https://github.com/williamthorsen/codeassembly/tree/main/packages/agents/content/skills/review-branch
Command: npx skills add https://github.com/williamthorsen/codeassembly --skill review-branch-williamthorsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing branch changes manually against tickets and specifications is slow and inconsistent, and findings often lack a durable record. This Skill performs a structured code review of the diff between the merge-base and HEAD, checks the implementation against ticket or PR specification sources, and saves a scored review artifact. ## Core Features & Use Cases - Diff-based code review: Reviews merge-base(HEAD, <diff-base>)..HEAD with categorized findings (FIXMEs, Warnings, TODOs, Recommendations, Suggestions, Legacy observations, Insights) and a score out of 10. - Specification compliance checking: Auto-resolves ticket sources from remote platform issues or local snapshots, compares acceptance criteria against the implementation, and renders compliance and cross-source consistency tables. - Artifact persistence: Saves each review as a timestamped run artifact under the ticket's run directory with canonical frontmatter, and emits lifecycle events for session tracking. - Use Case: Before merging a feature branch, run the review to get a scored report with actionable findings, a ticket compliance table, and next-step options saved for the team. ## Quick Start Review the changes on my current branch against the main branch and check them against the linked ticket.

Frequently Asked Questions about review-branch

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

FAQPage Schema
How do I review branch changes against a diff base?

Invoke the review with an optional --diff-base flag naming the reference branch; it reviews the range merge-base(HEAD, ref)..HEAD. Without the flag, it defaults to the project's default branch resolved from session context.

How does the review check implementation against a ticket?

It resolves specification sources from a remote platform issue or a local ticket snapshot, extracts acceptance criteria, and renders a compliance table marking each criterion Met, Partial, or Not addressed. With two or more sources it also renders a cross-source consistency verdict.

Can I force the review to use the remote ticket instead of a local snapshot?

Yes, pass --spec-source=remote or --spec-source=local to force candidate selection instead of the default recency comparison. If the named candidate is unavailable, the review stops and reports the missing source rather than silently switching.

What happens when a review finds no issues?

A no-findings review is a complete, valid outcome scored 10/10. The output renders condensed sections stating no action is required, with a technical assessment explaining why the change is correct and merge-ready.

Where are code review artifacts saved?

Reviews are saved as timestamped run artifacts under the ticket's run directory in the artifact base directory, following the repo's artifact conventions. Each review is a separate file so the chronological sequence forms the review history.