reviewing-code-prior-art-survey

Reviews prior-art survey artifacts against a twenty-two-condition acceptance bar and emits one verdict.

1|1|Updated May 24, 2026
One-click install
npx skills add https://github.com/bm629/agent-skills --skill reviewing-code-prior-art-survey-bm629
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: reviewing-code-prior-art-survey
Source: https://github.com/bm629/agent-skills/tree/main/skills/reviewing-code-prior-art-survey
Command: npx skills add https://github.com/bm629/agent-skills --skill reviewing-code-prior-art-survey-bm629

SYSTEM DOCUMENTATION & REQUIREMENTS

πŸ’‘ This Skill requires pyyaml, jsonschema, and includes references (resource) components.

What problem does it solve? When an agent produces an open-source prior-art search artifact β€” a keyword map, a per-angle search output, a per-repo extraction, or a synthesis report β€” someone must independently decide whether it is sound enough to feed the survey's downstream stages. Self-review by the producing agent approves its own work; this Skill applies a fixed, shared bar the reviewer cannot silently relax. ## Core Features & Use Cases - Twenty-two-condition acceptance gate: Judges keyword maps (conditions 1–6), search outputs (7–11), extractions (13–18), and synthesis reports (19–22), with proportionality (condition 12) gating every finding so thin-but-honest results pass. - Delegated deterministic checks: Runs the co-installed producer skill's validator (validate_prior_art.py) for schema and coverage conditions 7 and 11, requiring exit 0 and never re-implementing the checks. - Single machine-parseable verdict: Emits exactly one terminal VERDICT: approve|revise line (or the caller's named replacement), with revise findings naming the condition number, concrete gap, and what would satisfy it. - Use Case: After code-prior-art-survey produces a keyword map for a new capability, run this gate before search children execute it; on revise, route the condition-named findings back to the producer. ## Quick Start Use reviewing-code-prior-art-survey to judge the keyword map the producer just generated and give me the verdict with any findings.

Frequently Asked Questions about reviewing-code-prior-art-survey

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a prior-art search artifact before using it?β–Ό

Load this Skill with the artifact and the caller's scope context, then walk the applicable conditions from references/conditions.md. Run the producer's validator for the deterministic checks and emit one terminal VERDICT: approve or VERDICT: revise line with condition-named findings.

What artifacts does the prior-art survey review gate accept?β–Ό

It accepts keyword maps (full or delta mode), per-angle search outputs, per-repo extraction records including skip records, and synthesis reports with borrow-indexes. Each artifact type routes to its own subset of the twenty-two conditions.

Does reviewing-code-prior-art-survey work without the producer skill installed?β–Ό

No. The producer skill code-prior-art-survey must be co-installed because its package supplies the validator, schemas, and source registry that conditions 7 and 11 depend on. The validator also needs pyyaml and jsonschema on the invoking interpreter.

Why does the review approve a search output with many zero-hit cells?β–Ό

Zero-hit cells from reached sources are honest evidence of work in a thin domain, and condition 12 forbids revising on yield alone. A finding requires a named numbered condition plus a concrete gap, such as a zero recorded for a source that was never actually reached.

Can the reviewer fix or edit the artifact it is judging?β–Ό

No. The Skill is strictly review-only: it never authors, fixes, or re-derives an artifact. Findings are routed back to the producer skill, which performs the revision against the named conditions.