avad-review

Analyze local branch diffs or GitHub PRs against project checklists for pre-landing review.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/agwacom/avadbot --skill avad-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: avad-review
Source: https://github.com/agwacom/avadbot/tree/main/skills/avad-review
Command: npx skills add https://github.com/agwacom/avadbot --skill avad-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing Code Review analyzes diffs to surface structural issues using a project-specific checklist and guides teams toward safer landings before merging.

Core Features & Use Cases

  • Automated local and PR diff analysis against a customizable checklist.
  • Proactive guidance that helps catch scope drift, missing tests, and architectural risks before merge.
  • Use cases include pre-landing reviews for feature branches and PR reviews on open diffs.

Quick Start

Review the current branch diff or a GitHub PR and obtain actionable feedback to improve code quality before shipping.

Frequently Asked Questions about avad-review

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

FAQPage Schema
How do I automate code review for a local branch diff before merging?

Automated code review analyzes local branch diffs against a customizable checklist to identify structural issues. It reads project docs like CLAUDE.md and AGENTS.md for domain rules, providing structured feedback and suggested fixes before landing.

What is pre-landing code review and how does it catch architectural risks?

Pre-landing code review evaluates current code changes to surface actionable feedback before merging. It catches scope drift, missing tests, and architectural risks by applying a project-specific checklist to the diff analysis.

Can I use automated PR review for feature branches on GitHub?

Automated PR review adapts to evaluate GitHub PR diffs and local feature branch diffs. It references project files like GIT_WORKFLOW and TODOS to provide proactive guidance and suggested fixes for safer landings.

How do I customize a pre-merge code review checklist for my project?

Customize the review checklist by defining domain rules in project docs like CLAUDE.md and AGENTS.md. The review process reads these files sequentially to apply your specific architectural constraints and workflow guidelines to the diff analysis.

What's the best way to identify missing tests in a GitHub PR diff?

Identify missing tests by running an automated diff analysis against your project checklist. The review surfaces scope drift and missing test coverage proactively, providing structured results with suggested fixes before the code lands.

Does automated diff analysis work without CI/CD pipelines for pre-landing checks?

Automated diff analysis operates independently of CI/CD pipelines by evaluating local branch diffs directly. It reads project documentation files for domain rules and provides structured feedback with suggested fixes for immediate action.