skills.rest
AGMO-Inc
AGMO-IncOFFICIAL
Explore all skills by this author →
WebsiteGitHub

code-review

Automate structured code reviews with Stage 1, Stage 2, and Stage 3 audits.

4|1|Updated Mar 19, 2026
Search Tags:#automation#planning#qa#compliance#code-review#git-diff#audits
One-click install
npx skills add https://github.com/AGMO-Inc/agmo-everywhere --skill code-review-agmo-inc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/AGMO-Inc/agmo-everywhere/tree/main/skills/code-review
Command: npx skills add https://github.com/AGMO-Inc/agmo-everywhere --skill code-review-agmo-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews are time-consuming and error-prone. This Skill standardizes and automates the review process by guiding agents through a structured, two-stage evaluation against a formal plan, reducing manual overhead and increasing consistency.

Core Features & Use Cases

  • Stage-driven evaluation: Stage 1 Spec Compliance, Stage 2 Code Quality, Stage Completion Audit.
  • Plan-driven validation: checks that implementation matches plan TODOs, files touched, and acceptance criteria.
  • Clear output: returns PASS/FAIL with detailed rationale and traceability for audit.

Quick Start

Run the code-review skill on your current changes to initiate Stage 1 spec compliance review.

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 reviews to check implementation against a formal plan?▼

Automated code review standardizes evaluation by guiding agents through a structured two-stage process against a formal plan, reducing manual overhead and increasing consistency.

How does plan-driven validation work for code changes?▼

Plan-driven validation checks that implementation matches plan TODOs, files touched, and acceptance criteria, returning a clear PASS or FAIL with detailed rationale for traceability.

What is the best way to standardize spec compliance audits across repositories?▼

Standardizing spec compliance audits uses a stage-driven evaluation workflow, performing Stage 1 spec compliance and Stage 2 code quality checks across repositories.

Can I trigger code reviews after delivery instead of running them standalone?▼

Code review workflows support standalone reviews or reviews triggered after delivery, applying to code changes and implementation tasks across repositories.

What are the limitations of automated code quality audits?▼

Automated code quality audits are limited to evaluating changes against formal specs, plan TODOs, and acceptance criteria, requiring a pre-existing formal plan for validation.

Do I need a formal plan before running a spec compliance review?▼

A formal plan is required for spec compliance review to validate implementation by checking that code changes match plan TODOs, files touched, and acceptance criteria.

Related Skills

Explore More Software Engineering Skills→
aziglerazigler
8

spec

Convert scoped briefs and baselines into structured specification beads with test cases.

Community
Advanced
skwuwuskwuwu

gvm_audit

Verify GVM audit log integrity and export compliance reports.

Community
Intermediate
0xHarbs0xHarbs
1

test

Detect test frameworks, scope tests to changed code, and report coverage.

Community
Advanced
prof-danielcprof-danielc

speckit.checker

Run static analysis tools and aggregate results into a prioritized issue report.

Community
Advanced