brutal-project-review
Skill2 starsChanged 4 months agoMITView on GitHub
Systematically review a project subsystem-by-subsystem with resumable state tracking. Creates CRITICAL/MAJOR finding tasks through the work store resolved from BRUTAL.md.
In this repository25 other files it gives its agents.
- brutal-deepresearchSkill
- brutal-grillSkill
- brutal-idea-evalSkill
- brutal-inf-fix-loopSkill
- brutal-planSkill
- brutal-pr-finding-fixerSkill
- brutal-pr-fix-loopSkill
- brutal-pr-reviewSkill
- brutal-realitySkill
- brutal-reviewSkill
- brutal-specSkill
- brutal-swarmSkill
- brutal-ticketsSkill
- brutal-wayfinderSkill
- brutal-workerSkill
- codex-coopSkill
- design-jepa-modelsSkill
- factory-designSkill
- funcvec-dedupe-fixerSkill
- grill-meSkill
- handoffSkill
- opencode-delegateSkill
- rust-architecture-reviewSkill
- rust-pr-reviewSkill
- supply-chain-analyzerSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Read repo rules from AGENTS.md, CLAUDE.md, TARGET.md, and referenced workflow docs.
- Very specific: line 18
If BRUTAL.md is missing or incomplete, follow the integration setup flow.
- Distinctive: line 40
write temporary context under the resolved review-state directory
- Distinctive: line 44
write the subsystem report
- Distinctive: line 45
delete temporary context before stopping or reporting
- Very specific: line 46
Only create persisted work for validated CRITICAL and MAJOR findings by default.
- Distinctive: line 57
Before creating a finding, search existing state and work-store artifacts for the same fingerprint and these legacy source markers:
- Very specific: line 65
Create/update type:review-finding artifacts through the work-store adapter in its logical todo state, add progress to the parent when one …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Brutal Project Review
Review the project one subsystem at a time and persist actionable CRITICAL/MAJOR findings through the configured work-store adapter.
Required Context
- Read
../brutal-shared/integration-resolver.md. - Resolve the work store and load its support module before initializing state or creating findings.
- Read repo rules from
AGENTS.md,CLAUDE.md,TARGET.md, and referenced workflow docs. - If
BRUTAL.mdis missing or incomplete, follow the integration setup flow.
State Rules
- The local adapter uses its configured review-state path and local tasks.
- Remote adapters use
.brutal-workspace/review-state/only for resumable local review state. Exclude.brutal-workspace/through.git/info/excludebefore writing it and never create local work-store artifacts. - Preserve legacy manifest fields when resuming older runs, but write new
entries with adapter-neutral keys where practical:
work_store,work_store_project,parent_ref,findings_created.
Workflow
- Resolve or initialize the review manifest.
- Discover subsystems dynamically from behavior-defining files. Exclude
generated/vendor/build folders. Normalize ids as
01,02, etc. - Show the subsystem table and ask what to review: id/name/path,
all,pending,restart, orcancel. - For each selected subsystem:
- mark it
in_progress - gather relevant code, tests, migrations, APIs, configs, SQL, TOML, and docs
- write temporary context under the resolved review-state directory
- launch five reviewers when available: core correctness, reliability/tests, maintainability, performance/security, and simplification
- synthesize, dedupe, validate, and severity-check findings
- write the subsystem report
- delete temporary context before stopping or reporting
- mark it
- Only create persisted work for validated
CRITICALandMAJORfindings by default.
Finding Persistence
Use deterministic fingerprints:
<subsystem-id>|<canonical-file>|<line-or-symbol>|<severity>|<normalized-title>Before creating a finding, search existing state and work-store artifacts for the same fingerprint and these legacy source markers:
Source: brutal-project-review
Legacy sources: brutal-project-review, linear-brutal-project-review, gitlear-brutal-project-reviewCreate/update type:review-finding artifacts through the work-store adapter in
its logical todo state, add progress to the parent when one exists, and append
stable refs to the review manifest. Follow provider-specific read fallbacks and
prepare-before-create rules from the support module.
Finding bodies must include severity, subsystem, file/line, fingerprint, confidence, issue explanation, suggested fix, acceptance criteria, implementation notes, dependencies, and verification commands.
Final Response
Lead with findings by severity. Include work store, created/updated finding refs,
manifest path, parent ref, reviewed subsystem count, remaining subsystem count,
and recommend $brutal-swarm for parallel fixes or $brutal-worker for one
exact finding.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

