agentleFS
sm-wankosm-wanko/Human-on-exception/.claude/skills/independent-review/SKILL.md

independent-review

Skill1 starsChanged 46 days agoMITView on GitHub

Independently review a PR or change against Human-on-Exception's accepted decisions, SoT, tests, and documentation; report concrete defects and missing updates. Use when asked to review a PR or changed revision.

14 other projects use a version of this.

Adopted by

Most recently taken up by

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.
  • SentrySkill

    security-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

The file

Files
SKILL.md

Independent PR review

Act as a reviewer in a separate context from the implementation agent. Read and apply the canonical review contract in full, plus AGENTS.md, the accepted Questions / Answers and Issue AC, relevant concept / active ADR / Policy, the PR diff, tests, and applicable rules. An implementer's self-review or completion claim is not evidence. Review only; do not modify code during this review.

Required SoT/docs audit: derive every artifact affected by changed behavior and verify relevant implementation, tests, API/types/fakes/generated outputs, flow / ui / validation / db, transitions, and packs, including affected files absent from the diff. Distinguish current-state SoT from the agreed target contract; report concrete omissions and contradictions rather than demanding unrelated documentation or invalidating justified N/A.

Prioritize actual bugs, security, regressions, AC/Scope violations, and missing SoT/docs updates. For each finding give severity, path/line or missing path, supporting AC/rule, evidence or reproduction, impact, and correction direction. Write findings in the human-facing language selected by language-policy. State checks that could not be verified. If no concrete issue is found, respond concisely; do not claim independent review was completed without inspecting the evidence.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.