skills.rest
busboom-software-studio
busboom-software-studioOFFICIAL
Explore all skills by this author →
GitHub

code-review

Review code changes for correctness and quality with two-phase verdicts.

1|Updated Apr 29, 2026
Search Tags:#quality-assurance#coding-standards#code-review#acceptance-criteria#verdicts#phase-one#phase-two
One-click install
npx skills add https://github.com/busboom-software-studio/design-trainer --skill code-review-busboom-software-studio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/busboom-software-studio/design-trainer/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/busboom-software-studio/design-trainer --skill code-review-busboom-software-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill reviews code changes through a two-phase process: first correctness against acceptance criteria, then quality against coding standards. It does not implement code or fix issues — it reports findings.

Core Features & Use Cases

  • Phase 1: Correctness checks that the implementation satisfies every acceptance criterion, producing PASS or FAIL and highlighting missing aspects.
  • Phase 2: Quality review for coding standards, security, and maintainability, with a phase-2 verdict and prioritized issues.
  • Use Case: In a pull request, run the two-phase review to verify compliance before merging and to surface gaps for remediation.

Quick Start

Submit a code change for review and obtain a two-phase verdict with findings.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I verify code changes meet acceptance criteria before merging a pull request?▼

A two-phase code review verifies implementation correctness against acceptance criteria, producing a PASS or FAIL verdict and highlighting any missing requirements in the pull request.

What is a two-phase code review process for correctness and quality?▼

A two-phase code review first checks implementation correctness against acceptance criteria, then assesses code quality against standards for security and maintainability, yielding structured PASS or FAIL verdicts for each phase.

Can I use automated code review to assess test coverage and maintainability across different programming languages?▼

Yes, this code review applies to pull requests and commits across languages, verifying proper behavior, test coverage, and secure maintainable implementation while outputting structured findings and suggested fixes.

Does the code review automatically fix coding standard violations it finds?▼

No, the code review does not implement code or fix issues; it reports findings by providing a structured list of identified issues alongside suggested fixes for remediation.

What is the best way to surface security and maintainability gaps in a pull request?▼

Running Phase 2 of a two-phase code review surfaces security and maintainability gaps by assessing code quality against standards and producing prioritized issues for remediation.

Related Skills

Explore More Software Engineering Skills→
tomas-utomas-u
1

code-review

Analyze code diffs against stories, tests, and coding standards.

Community
Advanced
zhnnky329zhnnky329
452

quality-assurance-auditor

Audit mathematical modeling solutions and generate a QA report with pass/fail verdicts.

Community
Advanced
idiaz01idiaz01
3

springboot-verification

Orchestrates build, static analysis, tests with Jacoco coverage, and security scans for Spring Boot projects in CI pipelines.

Community
Advanced
J03Fr0stJ03Fr0st

doubt-driven-development

Review code changes with an adversarial reviewer focused on disproof.

Community
Advanced