skills.rest
compartmentdev
compartmentdevOFFICIAL
Explore all skills by this author →
WebsiteGitHub

review-a-change

Identify owning packages and run parallel subagent review passes on repository changes.

229|5|Updated May 25, 2026
Search Tags:#automation#subagents#delegation#parallel#review#code-review
One-click install
npx skills add https://github.com/compartmentdev/compartment --skill review-a-change
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-a-change
Source: https://github.com/compartmentdev/compartment/tree/main/.codex/skills/review-a-change
Command: npx skills add https://github.com/compartmentdev/compartment --skill review-a-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review in the compartment repo can be inconsistent and slow; this skill enforces a structured, multi-pass review using delegated subagents to surface findings early and comprehensively.

Core Features & Use Cases

  • Parallel subagent passes for contracts-and-architecture, runtime-hygiene, docs-drift, and validation, plus subsequent 1-3 slice passes grouped by owning package.
  • No main-agent-only fallback; main integration aggregates findings from all passes while preserving separation of concerns.
  • Findings are reported with precise file and line references to guide targeted fixes.
  • Uses source-of-truth resources like AGENTS.md, docs/layers/README.md, and touched package docs to anchor the review.

Quick Start

Invoke the skill with $review-a-change to start a parallel, delegated code review of the current repository diff.

Frequently Asked Questions about review-a-change

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

FAQPage Schema
How do I automate parallel code review for repository diffs?▼

Automated parallel code review launches separate subagents for contracts, runtime hygiene, docs drift, and validation, then splits the remaining surface into package-level slices to surface bugs and regressions with precise file and line references.

What is a delegated subagent workflow for code review?▼

A delegated subagent code review workflow distributes distinct review passes across parallel agents to preserve separation of concerns, with the main agent aggregating findings without falling back to single-agent execution.

How do I identify contracts and runtime surface areas touched by a code change?▼

Identifying touched runtime surface requires locating the owning package, entry boundary, contracts, and the single canonical path affected by the diff, anchoring the analysis to source-of-truth documentation like AGENTS.md.

Can I use automated code review to find documentation drift?▼

Yes, automated code review can detect documentation drift by launching dedicated parallel subagents that compare updated code contracts against existing package docs to surface inconsistencies.

Does this parallel code review workflow edit or resolve files automatically?▼

No, this parallel code review workflow only reports findings with file and line references to guide targeted fixes; it does not edit or resolve files during the review process.

Related Skills

Explore More Software Engineering Skills→
u9401066u9401066

file-restructurer

Restructure project files with dry-run previews and rollback backups.

Community
Advanced
jaisonerickjaisonerick

fix-bugs

Reproduce QA-reported failures with failing tests and apply minimal code fixes.

Community
Advanced
KrismithReddy12KrismithReddy12

health

Calculate a weighted 0-10 code quality score from linters and test runners.

Community
Advanced
doanchienthangdevdoanchienthangdev
4

Stacked Diffs Workflow

Implement stacked diffs workflows for breaking large code changes into reviewable PRs.

Community
Advanced