independent-review
Skill0 starsChanged 2 months agoMITView on GitHub
Review a candidate change without modifying it, prioritizing concrete correctness and compatibility findings over stylistic preferences.
14 other projects use a version of this.
Adopted by
Most recently taken up by
- on-keyday/agent-harnesstheir own version, first seen Nov 16, 2026
- bcmyguest/personal-skillstheir own version, first seen Nov 8, 2026
- DnsQueen/orcinus-skillstheir own version, first seen Nov 8, 2026
- chocomyong/harness-kittheir own version, first seen Nov 1, 2026
- woodbeary/later-dogtheir own version, first seen Nov 1, 2026
- itsofficialadi/boundifftheir own version, first seen Oct 25, 2026
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- karero/croftweaver★ 10same name
- karero/website-builder★ 10same name
- ramboz/jig★ 7same name
- RizwanZafaris/product-manager-OS★ 4same name
- DnsQueen/orcinus-skills★ 3same name
- chocomyong/harness-kit★ 2same name
- on-keyday/agent-harness★ 2same name
- woodbeary/later-dog★ 2same name
- NecturaLabs/AgentSkills★ 1same name
- renatodvc/rstack★ 1same name
4 more not listed
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 repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- elixir-docsSkill
- feature-planSkill
- multi-repo-changeSkill
- package-readinessSkill
- parallel-deliverySkill
- safe-refactorSkill
- security-reviewSkill
- stack-elixirSkill
- stack-nextjsSkill
- stack-phoenix-liveviewSkill
- stack-rustSkill
- stack-svelteSkill
- systematic-debuggingSkill
- technical-writingSkill
- ui-validationSkill
- unslopSkill
- worktree-integrationSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Read applicable AGENTS.md review rules.
- Distinctive: line 13
Check correctness, failure paths, boundary cases, concurrency/resource behavior, compatibility, unintended scope, and test adequacy.
- Distinctive: line 35
If no consequential issue is found, state what was reviewed and what remains unverified.
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Independent review
Procedure
- Pin the review to an exact candidate SHA or immutable diff.
- Read applicable
AGENTS.mdreview rules. - Inspect the diff and enough surrounding code to understand behavior and contracts.
- Check correctness, failure paths, boundary cases, concurrency/resource behavior, compatibility, unintended scope, and test adequacy.
- Compare implementation against acceptance criteria rather than the author's narrative.
- Validate important concerns with code/tests/commands when read-only execution permits.
For changed public or shared interfaces, follow contract impact. Check consequential documentation claims against the candidate, including examples, compatibility promises, and intentional internal API visibility. Use elixir-docs when applicable; separate generation evidence from executed examples and reader review.
For agent or skill changes, inspect triggers and exclusions, ownership, supported configuration, referenced resources, and representative positive/negative cases. Syntax checks do not establish correct selection or execution. Do not treat phrasing preferences as failures without a concrete effect on the reader or task.
Approval applies to the inspected candidate. Later edits require the new revision and refreshed affected review and validation; tests alone cannot approve an unreviewed rewrite.
Return one findings report to the coordinator. Deduplicate repeated findings by failure mode and affected contract/location; distinguish unresolved findings from new evidence. Do not dispatch repairs or broaden the plan. Label an interrupted or budget-exhausted review incomplete, with the coverage gap; it cannot approve the candidate.
Findings
For consequential findings include:
- severity;
- affected file/symbol or behavior;
- evidence;
- concrete failure mode;
- suggested direction, without rewriting the production change yourself.
If no consequential issue is found, state what was reviewed and what remains unverified.
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.

