review-integration
Skill0 starsChanged 7 days agoMITView on GitHub
Use when reviewing a plan, a diff or a wave of agent work against architecture, consistency, performance and test standards - plan-reviewer, qa-verifier and product-reviewer procedure, reject list and multi-agent integration.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- timholy/claude_configtheir own version, first seen Oct 20, 2026
- elastic/integration-skillstheir own version, first seen Aug 25, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- timholy/claude_config★ 75same name
- elastic/integration-skills★ 16same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository35 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- skills/work/platforms/claude.mdCLAUDE.md
- llms.txtllms.txt
- clarifySkill
- consistencySkill
- debuggingSkill
- documentationSkill
- featureSkill
- hexagonalSkill
- initSkill
- jobs-and-state-machinesSkill
- lang-clojureSkill
- lang-cppSkill
- lang-csharpSkill
- lang-elixirSkill
- lang-erlangSkill
- lang-goSkill
- lang-javaSkill
- lang-kotlinSkill
- lang-phpSkill
- lang-pythonSkill
- lang-rubySkill
- lang-rustSkill
- lang-scalaSkill
- lang-swiftSkill
- lang-typescriptSkill
- memorySkill
- parallel-workSkill
- performanceSkill
- qualitySkill
- reportSkill
- statusSkill
- testingSkill
- workSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Read only the acceptance criteria, the diff, the affected package AGENTS.md, the reported tests and benchmarks.
- Very specific: line 47
Use templates/PLAN_REVIEW.md.
- Distinctive: line 55
Before accepting a wave: collect claims reports.
≈ “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
Review and integration
Load
Read only the acceptance criteria, the diff, the affected package AGENTS.md, the reported tests and benchmarks. Definition of done: specs/WORKFLOW.md §8. Open more source only when needed (specs/CONTEXT_DISCIPLINE.md §19).
Review order
- correctness
- architecture ownership (
specs/ARCHITECTURE.md §29) - consistency: clock, RNG, ordering, idempotency (
skills/consistency) - invariants
- data complexity and performance
- concurrency and the pack's race policy (WORKFLOW §6)
- persistence, API and config compatibility
- tests: behaviour named, failure paths, no weakened tests
- API and readability per the language's idioms (
skills/lang-<id>/idioms.md; Go:specs/languages/go/RULES.md §51) - documentation: package
AGENTS.mdfor changed contracts - observability: errors explicit, logs and metrics where operators need them
Reject
- an unrelated broad refactor;
- a weakened or deleted test;
- a duplicate canonical type;
- domain depending on an adapter, transport or storage type;
- global mutable state, import-time registration (Go
init()); - a thread, task or goroutine per item without a bound;
- the wall clock or a global RNG in authoritative code (the pack's
impure_calls); - decisions from hash-map iteration order;
- a silent persisted-schema or API break;
- a retried operation without an idempotency key;
- a new hot global scan or N+1 query;
- a performance claim without a benchmark;
- unbounded external input;
- hand-edited generated code;
- business rules in a handler or repository;
- a claim without evidence, or evidence the reviewer cannot re-run.
Reviewing a plan (plan-reviewer)
Use templates/PLAN_REVIEW.md. Check completeness against specs/PARALLEL_WORK.md §1: contract, waves table, per-agent blocks, disjoint ownership, models with reasons, QA pairing, proof plan. Findings are numbered, each with what, why and a suggested change; only blockers block.
Verifying claims (qa-verifier)
Independently re-run the evidence, read the code, attack the claim with edge cases and the pack's race policy, and report per claim VERIFIED or FAILED with a repro (templates/QA_VERDICT.md). List unclaimed problems separately. Do not fix code.
Multi-agent integration
Before accepting a wave: collect claims reports; compare interface changes; find overlapping files; resolve each canonical contract once; merge in dependency order; run loops gate (every detected pack) and the affected benchmarks (specs/PARALLEL_WORK.md §6). Never keep two competing abstractions to "clean up later".
Report check
Each report states: changed contracts, invariants, tests, benchmark delta, consistency impact, compatibility impact, limits and follow-ups. Do not request chain-of-thought.
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.

