code-review

Name: code-review
Availability: InStock
Author: Busboom-Foo

Assess code changes against acceptance criteria with a two-phase review workflow.

Updated Apr 3, 2026

Search Tags:#testing #code-quality #quality-assurance #code-review #acceptance-criteria #engineering-review #review-process

Ready to run

npx skills add https://github.com/Busboom-Foo/meetupfu --skill code-review-busboom-foo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Busboom-Foo/meetupfu/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/Busboom-Foo/meetupfu --skill code-review-busboom-foo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Two-phase code review reduces manual overhead by evaluating code changes for correctness against acceptance criteria and quality against coding standards, providing structured feedback rather than ad-hoc comments.

Core Features & Use Cases

Two-phase evaluation: Phase 1 checks correctness against acceptance criteria; Phase 2 checks quality, maintainability, security, and architectural consistency.
Decision outputs: Phase 1 yields PASS or FAIL per criterion; if Phase 1 passes, Phase 2 identifies issues with severity levels and actionable recommendations.
Traceability: Verifies that tests exist for each criterion and that they pass.

Quick Start

Review the latest pull request against the ticket's acceptance criteria and coding conventions to generate a Phase 1 PASS/FAIL verdict and Phase 2 findings.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I automate code review against acceptance criteria?▼

Automate code review against acceptance criteria using a two-phase evaluation workflow. Phase 1 checks correctness by yielding a PASS or FAIL verdict per criterion, while Phase 2 assesses code quality and maintainability if Phase 1 passes.

What is a two-phase code review process?▼

A two-phase code review process splits evaluation into correctness and quality checks. Phase 1 verifies code changes against acceptance criteria with PASS or FAIL outcomes, and Phase 2 identifies severity-level issues for maintainability and security.

How do I verify that tests exist for acceptance criteria during a code review?▼

Verify tests for acceptance criteria during code review by applying Phase 1 traceability checks. This process ensures that tests exist for each criterion and confirm they pass before proceeding to quality assessment.

Does this code review workflow check for security and architectural consistency?▼

Yes, the code review workflow checks for security and architectural consistency. During Phase 2, it evaluates code quality, maintainability, security, and architectural consistency, providing actionable recommendations with severity levels.

What is the best way to structure pull request feedback for engineering reviews?▼

Structure pull request feedback for engineering reviews by using a two-phase workflow. Output Phase 1 PASS or FAIL verdicts per criterion, then generate Phase 2 findings with severity levels and actionable recommendations for quality issues.