agentsclimarketplace
Sign in

Judge review findings

Skill aictrl-dev/skills/skills/judge-review-findings

Judge untriaged code-review findings for the current pull-request head as TRUE, FALSE, or UNCERTAIN and choose FIX, DEFER, or IGNORE without changing code. Use when the user says "triage review findings", "judge these comments", "which findings are real", or "decide what to fix from this review".From its SKILL.md

Install
npx -y skills add aictrl-dev/skills --skill judge-review-findings

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.9 KB, 592 tokens by cl100k_base, as published. Nobody here has run it

Judge Code-Review Findings

Independently verify review findings against the exact current revision before any remediation begins.

Workflow

  1. Resolve the pull or merge request and current head SHA. Load only findings created for that head; mark older-head findings STALE and do not silently apply them.
  2. For each untriaged finding, inspect the cited line, surrounding code, callers, tests, configuration, and relevant contract. Reproduce the scenario when safe and useful.
  3. Judge truth:
    • TRUE — evidence proves the finding and impact on the current head.
    • FALSE — the finding is contradicted, already prevented, outside the change, or based on an incorrect assumption.
    • UNCERTAIN — available evidence cannot resolve a material fact.
  4. Choose an action independently from truth:
    • FIX — remediate in the current change.
    • DEFER — valid but deliberately tracked outside this change, with a concrete reason and destination.
    • IGNORE — no remediation is warranted, normally paired with FALSE.
  5. Record confidence and evidence. A reviewer assertion is not evidence by itself.
  6. Persist judgments through the native review/provider capability only when explicitly requested. Do not modify code.
  7. Summarize counts, blockers, stale findings, and the ordered remediation set.

Judgment format

| Finding | Head | Verdict | Action | Confidence | Evidence and rationale |
|---|---|---|---|---|---|
| <id/title> | `<sha>` | TRUE/FALSE/UNCERTAIN/STALE | FIX/DEFER/IGNORE | high/medium/low | <specific code/test evidence> |

For every DEFER, name the follow-up issue or return a complete follow-up draft. For every UNCERTAIN, name the smallest experiment or missing fact that would decide it.

Boundaries

  • Judge; do not fix, commit, push, reply, dismiss, or merge.
  • Do not downgrade a true high-impact finding merely to keep scope small.
  • Do not accept a finding solely because an automated reviewer produced it.
  • Do not apply a judgment to a different head revision.

Built by aictrl.dev. This skill teaches the workflow; aictrl operationalizes it — grounded in your backlog, team standards, and codebase knowledge graph. See how →

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most review quality skills give in 592 tokens

Counted across 1,273 of the 2,403 authors here whose files we hold, read 2026-09-06

  • Ask one question at a timein 63 of 1273, across 62 files
  • Provide a recommended answer for each questionin 47 of 1273, across 45 files
  • Rank findings by severityin 44 of 1273
  • Use parameterized queries for database accessin 38 of 1273, across 20 files
  • Validate all user input with schemasin 33 of 1273, across 15 files
  • Store secrets in environment variablesin 32 of 1273, across 14 files
  • Explore the codebase to answer questionsin 31 of 1273, across 29 files
  • Store tokens in httpOnly cookiesin 30 of 1273, across 12 files
  • Implement rate limiting on API endpointsin 30 of 1273, across 12 files
  • Sanitize user-provided HTMLin 29 of 1273, across 11 files
  • Return generic error messages to usersin 28 of 1273, across 10 files
  • Cite file and line for every findingin 28 of 1273, across 25 files

Said here and by no other author read

  • Load only findings for current head
  • Mark older findings as stale
  • Inspect cited code and surrounding context
  • Reproduce scenarios when safe
  • Judge truth independently
  • Choose action independently

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.