agentleFS
tbhbtbhb/vale-ai-tells/.claude/skills/codex-review-pr-description/SKILL.md

codex-review-pr-description

Skill118 starsChanged 37 days agoMITView on GitHub

Independently review PR_AGENTDESC.md against the branch it would publish, covering unsupported claims, counting, provenance filler, diff restatement, whole-branch fit, and branch coherence. Use as a fresh delegated reviewer before codex-pr publishes or updates any pull request.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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
  1. Distinctive:

    Don't repeat mechanical validator rules.

    line 19
  2. Distinctive:

    If the draft passes, record the exact reviewed bytes yourself:

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Review a pull request description

Act as an independent reviewer. Don't edit PR_AGENTDESC.md or rely on the writer's explanation.

Clear any older review before reading:

bash .agents/skills/codex-pr/scripts/record-review.sh <repo root> clear

The argument is the repository root. Default to the current directory. Read the draft, its base: field, <base>..HEAD commit messages, <base>...HEAD name-status and diff, and .github/pull_request_template.md. A missing draft or empty branch is a finding.

Don't repeat mechanical validator rules. Judge:

  • truthfulness: the branch supports each claim and each verification command
  • substance: sections answer the template rather than restating the diff
  • fit: title, summary, labels, and draft status cover the whole branch
  • coherence: the branch forms one mergeable and revertible change
  • prose integrity: omit counts and selling language, along with process, model, and tool provenance

Name exact offending text and a specific correction. Sweep the whole draft for further instances of each fault before returning.

If the draft passes, record the exact reviewed bytes yourself:

bash .agents/skills/codex-pr/scripts/record-review.sh <repo root>

Then return only:

VERDICT: PASS

Otherwise leave the digest cleared. Return only:

VERDICT: CHANGES REQUIRED

1. [truthfulness|substance|fit|coherence] <problem>
   text: <exact text>
   fix:  <specific correction>

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.