independent-review
Skill2 starsChanged 30 days agoApache-2.0View on GitHub
Have a separate cloud session review a published PR at its exact current commit, and treat its verdict as valid for that commit only.
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
- itsofficialadi/boundifftheir own version, first seen Oct 25, 2026
- karero/website-buildertheir own version, first seen Oct 14, 2026
Used with
Projects with it also use security-review.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
SentrySkillsecurity-review
Finds exploitable application security vulnerabilities in code changes. Use for Warden security scans, appsec review, OWASP-style checks, authentication or authorization bugs, injection, XSS, SSRF, path traversal, secrets, unsafe crypto, webhook verification, open redirects, or sensitive data exposure.
Also in 4 projects that use this
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
- NecturaLabs/AgentSkills★ 1same name
- renatodvc/rstack★ 1same name
- sm-wanko/Human-on-exception★ 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 repository43 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- architectSkill
- benchmark-checklistSkill
- correct-recurring-errorsSkill
- create-verification-skillSkill
- independent-reviewSkill
- maintain-verification-skillSkill
- monitor-and-shipSkill
- orchestrate-cloud-workSkill
- setup-laterdogSkill
- verify-laterdogSkill
- architectSkill
- benchmark-checklistSkill
- correct-recurring-errorsSkill
- create-verification-skillSkill
- maintain-verification-skillSkill
- monitor-and-shipSkill
- orchestrate-cloud-workSkill
- setup-laterdogSkill
- verify-appSkill
- verify-laterdogSkill
- architectSkill
- benchmark-checklistSkill
- correct-recurring-errorsSkill
- create-verification-skillSkill
- independent-reviewSkill
- maintain-verification-skillSkill
- monitor-and-shipSkill
- orchestrate-cloud-workSkill
- setup-laterdogSkill
- verify-laterdogSkill
- architectSkill
- benchmark-checklistSkill
- correct-recurring-errorsSkill
- create-verification-skillSkill
- independent-reviewSkill
- maintain-verification-skillSkill
- monitor-and-shipSkill
- orchestrate-cloud-workSkill
- setup-laterdogSkill
- verify-laterdogSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use once a job's PR is published, before anyone calls it ready.
- Very specific: line 14
Let it run: Follow the review job with inspect_cloud_job until it settles.
“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
Use once a job's PR is published, before anyone calls it ready. The run that wrote a change does not approve it. Use the later.dog MCP server. Discover tools by the names below; client-specific prefixes may vary.
Procedure
- Pin the commit.
inspect_cloud_jobon the job: note the PR and itsheadSha. - Start the review with
review_cloud_joband a newrequestKey. Pass aprofileIdon another backend when one is connected; a second account on the same model is the same reviewer twice, so say which you used. The supervisor briefs a separate cloud run to read the requirements, the diff, the code around it and the tests, and to write only.laterdog-review.json: theheadSha, averdictofpassorchanges_requested, and asummaryof its findings and what it actually checked. That file is kept as evidence and never reaches the product branch. - Let it run. Follow the review job with
inspect_cloud_jobuntil it settles. Do not resume or resubmit it to see whether it is alive. - Read the summary, not only the verdict. A pass that does not say what was checked, or that admits something important could not be run or inspected, counts as a finding.
- Watch the head. A new commit on the PR (a repair run, a push) voids the review; review the new head. No verdict comes from green CI or from a worker's confidence in its own work.
Report
The PR, the commit reviewed, the reviewer's profile, the verdict, the findings, and what the reviewer could not check.
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.

