beads-reviewer

Review Beads task commits and diffs to assess merge readiness.

Updated Jan 26, 2026

Search Tags:#automation #beads #review #task-management #code-review #git-diffs #merge-verdict

Ready to run

npx skills add https://github.com/vega113/beads-orchestration-skills --skill beads-reviewer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: beads-reviewer
Source: https://github.com/vega113/beads-orchestration-skills/tree/main/beads-reviewer
Command: npx skills add https://github.com/vega113/beads-orchestration-skills --skill beads-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Independently review a Beads task implementation (commits + diff + checks), write findings back to the task, and provide a merge verdict. Use when reviewing code, checking implementations, or validating task branches before merge.

Core Features & Use Cases

Independent review of Beads task branches against the base branch
Document findings back into the Beads task with blockers, important issues, and a final verdict
Verify that changes meet acceptance criteria, align with the task plan, and maintain project quality
Provide a clear merge verdict and confidence score to guide orchestration

Quick Start

Review the Beads task by comparing the feature branch to the base and document findings in the task using the provided review template.

Frequently Asked Questions about beads-reviewer

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

FAQPage Schema

How do I automate code review for task branches before merging?▼

You can automate code review for task branches by analyzing commits, diffs, and checks to assess merge readiness. This independent review documents blockers, important issues, and a clear merge verdict back into the task, citing file paths and providing a confidence score.

What is an independent task review and how does it validate merge readiness?▼

An independent task review validates merge readiness by examining git diffs and commits to ensure changes meet acceptance criteria and maintain project quality. It produces a concise, structured review that cites file paths and provides a final Ready or Not ready verdict with a confidence score.

How do I document code review findings directly into a task management system?▼

Documenting code review findings into a task management system involves writing blockers, important issues, and a final merge verdict back into the Beads task. The structured review uses a provided template to cite file paths and record a confidence score for orchestration guidance.

Can I use automated merge verdicts to validate git diffs for task implementations?▼

Yes, you can validate git diffs for task implementations by reviewing commits and checks against the base branch. The review verifies that changes align with the task plan, documents blockers, and outputs a Ready or Not ready merge verdict with an associated confidence score.

Does independent code review work with existing task branches and base branch comparisons?▼

Independent code review works by comparing existing task branches against the base branch to evaluate implementation quality. It checks whether changes meet acceptance criteria, documents important issues with cited file paths, and provides a final merge verdict with a confidence score.

When should I not use an automated merge verdict for code review?▼

Automated merge verdicts for code review should not be used as the sole validation when complex architectural changes require deep contextual understanding. The review provides a confidence score and structured findings, but human oversight remains necessary for nuanced architectural decisions beyond diff analysis.