skills.rest
rbah31
rbah31COMMUNITY
Explore all skills by this author →
GitHub

review

Analyze build output and generate a structured Findings report.

5|Updated Mar 9, 2026
Search Tags:#qa#static-analysis#quality-assurance#code-review#sprint#pull-request#build-review
One-click install
npx skills add https://github.com/rbah31/claude-code-workflow --skill review-rbah31
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/rbah31/claude-code-workflow/tree/main/.claude/skills/review
Command: npx skills add https://github.com/rbah31/claude-code-workflow --skill review-rbah31

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review workflow. Reviews the build output for quality, conventions, performance, security, and test coverage. Use after a build phase is complete, or when the user says "review", "check the code", "PR review", "quality check", or "is this good". Also use when the user wants a second opinion on code that was just written. Always use this skill after /build.

Core Features & Use Cases

  • Core reviewers (always invoked): code-reviewer for quality, conventions, readability, maintainability; qa-tester for test coverage, missing edge cases, test quality.
  • Conditional reviewers based on modified files to broaden coverage (e.g., infrastructure, UX).
  • Consolidated findings: a single review output to guide fixes and decisions.

Quick Start

Invoke the review skill after a build to analyze the latest build-output and present a findings report.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate code review after a build completes?▼

Automated post-build code review analyzes the latest build output to identify quality, convention, performance, security, and test coverage issues. You invoke the review process after each build phase to receive a structured findings report.

What is included in a pull request quality check?▼

A pull request quality check enforces core reviewers for code quality, readability, maintainability, and test coverage, while applying conditional reviewers for infrastructure or UX concerns based on modified files.

When do I need a static analysis report during a sprint?▼

Static analysis reports are needed during sprint reviews or after each build phase to provide a second opinion on recently written code, ensuring quality and test coverage standards are met before merging.

Does post-build review check for missing test coverage and edge cases?▼

Post-build review executes a dedicated qa-tester to check test coverage, identify missing edge cases, and evaluate overall test quality alongside standard code conventions and security findings.

Can I get a consolidated findings report for infrastructure and UX code changes?▼

Consolidated findings reports include conditional reviewers that automatically broaden coverage to analyze infrastructure or UX concerns based on the specific files modified in the build output.

What are the limitations of automated build review?▼

Automated build review is limited to analyzing the latest build-output and requires a completed build phase to execute. It does not review code independently without prior build execution or user invocation.

Related Skills

Explore More Software Engineering Skills→
tech-with-sethtech-with-seth
4

create-unit-test

Create Vitest unit tests co-located with source files using project templates.

Official
Intermediate
darkroomengineeringdarkroomengineering
41

review

Review TypeScript, React, and architecture for quality, security, and correctness issues.

Official
Advanced
thktthkt
11

test

Execute project tests and analyze code coverage with package managers and linters.

Community
Intermediate
y-miyazakiy-miyazaki
1

go-review

Guide manual Go code reviews across correctness, security, performance, and idioms.

Community
Advanced