avadbeta-review

Analyze branch diffs to identify defects that tests miss.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/agwacom/avadbeta --skill avadbeta-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: avadbeta-review
Source: https://github.com/agwacom/avadbeta/tree/main/codex-plugin/skills/avadbeta-review
Command: npx skills add https://github.com/agwacom/avadbeta --skill avadbeta-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evidence-backed code review of the current branch diff against the base branch. Find defects the tests do not catch, report them as specific findings the user can act on, and stop.

Core Features & Use Cases

  • Reads and evaluates the diff between current branch and base to surface defects not covered by tests.
  • Produces actionable findings with precise lines and rationale for reviewer decisions.
  • Supports preflight and diff-based feedback workflows for PRs, hand-offs, and risk sweeps.

Quick Start

Run the /avadbeta-review command on a branch with changes to generate a findings report.

Frequently Asked Questions about avadbeta-review

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

FAQPage Schema
How do I automate pre-landing code reviews for my branch diff?

Automate pre-landing code reviews by running the review command on your current branch. It analyzes the diff against the base branch to identify defects tests miss, reporting specific actionable findings with precise lines for your PR.

What is evidence-based code review and how does it work with diffs?

Evidence-based code review evaluates changed files strictly from the branch diff. It reads new and modified files to surface defects not covered by tests, producing rationale-backed findings to guide reviewer decisions during pre-landing workflows.

Can I use this for risk assessment sweeps before merging a pull request?

Yes, you can use this for risk assessment sweeps before merging. It operates on changed files within the diff to evaluate impact and identify potential risks, generating a findings report to support your hand-offs and PR feedback workflows.

Does the code review fix the defects it finds in the diff?

No, the code review does not fix defects automatically. It operates strictly on the diff to read changed files and reports specific actionable findings, stopping there unless you explicitly ask it to apply fixes to the identified issues.

What is the best way to find defects that automated tests miss?

The best way to find missed defects is executing a diff-based analysis against your base branch. It reads changed and new files to pinpoint uncovered issues, delivering precise actionable findings with rationale for your pre-landing review.