code-review

Automate iterative code review against requirements and architectural standards.

10|2|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/raddue/crucible --skill code-review-raddue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/raddue/crucible/tree/main/skills/code-review
Command: npx skills add https://github.com/raddue/crucible --skill code-review-raddue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of code review, helping to catch bugs, architectural issues, and ensure adherence to requirements before code is merged.

Core Features & Use Cases

  • Automated Code Analysis: Dispatches a subagent to review code changes against specified requirements.
  • Iterative Feedback Loop: Facilitates multiple rounds of review and revision to improve code quality.
  • Use Case: Before merging a new feature, you can use this skill to get an automated review that checks for critical bugs, adherence to the original plan, and overall code health.

Quick Start

Use the code-review skill to review the changes between the last commit and the current commit.

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 before merging new features?

Automated code review dispatches a subagent to verify implemented code meets specified requirements and architectural standards before integration. It checks for critical bugs, adherence to the original plan, and overall code health to ensure production readiness.

What is an iterative code review process for development workflows?

An iterative code review process facilitates multiple rounds of automated feedback and revision to improve code quality. This ensures critical and important issues are addressed progressively before code integration, maintaining high quality assurance standards throughout the development workflow.

Can I check git code changes against original requirements automatically?

Yes, you can review code changes between commits automatically to verify they meet original requirements. The automated analysis checks implemented code against specified requirements, architectural standards, and production readiness criteria.

Does automated code review work with my existing git development workflow?

Automated code review integrates into existing git development workflows by analyzing code changes between commits. It requires no additional dependencies and works by dispatching subagents to verify code quality, architectural adherence, and requirement compliance.

What is the best way to catch architectural issues before code integration?

The best way to catch architectural issues before integration is using automated code analysis that checks implemented code against specified architectural standards. This iterative review process ensures critical structural problems are identified and addressed before merging.

When do I need automated quality assurance for code changes?

You need automated quality assurance for code changes when verifying if implemented code meets specified requirements and is production-ready before merging. It is essential for catching critical bugs and architectural issues during the development workflow.