audit-implement

Audits finished branch diffs by spawning parallel review agents and reproducing runtime claims.

5|Updated Sep 9, 2017
One-click install
npx skills add https://github.com/hpcsc/dotfiles --skill audit-implement-hpcsc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit-implement
Source: https://github.com/hpcsc/dotfiles/tree/main/link/common/dot-config/.config/opencode/skills/audit-implement
Command: npx skills add https://github.com/hpcsc/dotfiles --skill audit-implement-hpcsc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After you build a feature yourself, self-review is biased and shallow. This Skill runs an adversarial, independent audit over your branch diff: specialist review agents challenge the code from lenses that never saw you write it, and every runtime claim must be reproduced by execution before it counts as a finding. ## Core Features & Use Cases - Multi-lens parallel review: Semantic, guidelines, test-integrity, concurrency, and performance lenses run per language, each owning its files while seeing the rest of the diff as context. - Evidence-based refutation: Runtime findings must be reproduced with a failing test, race run, benchmark, or direct invocation; quality findings must cite a rule at a specific line, or they are dropped. - Ranked, re-graded report: Surviving findings are re-graded against one severity rubric, deduplicated before refutation, and reported with confidence levels and coverage gaps. - Use Case: After finishing a green feature branch, run clerk audit run --base main --brief "..." --request "..." to get a JSON report of confirmed defects before merging. ## Quick Start Ask the assistant to audit the current branch against main with clerk audit run, passing a brief and the original request verbatim.

Frequently Asked Questions about audit-implement

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

FAQPage Schema
How do I audit a finished branch with AI review agents?▼

Run clerk audit run with --base set to the ref the work started from, a one-sentence --brief, and the original --request verbatim. The command scopes the diff, spawns one agent per applicable lens, refutes each finding, and returns a ranked JSON report.

What review lenses does an automated code audit run?▼

The audit runs semantic and guidelines lenses per language, plus test-integrity when tests changed, and concurrency or performance lenses only when the scoping pass finds real signals. Skipped lenses are reported in lenses_not_run rather than passing silently.

Does the audit require claude or opencode installed?▼

Yes, a coding harness must be on PATH because the round spawns headless agents through whichever it finds. Without one, clerk audit run refuses to start rather than reporting a clean audit; you can also pass --harness-cmd.

How are audit findings verified before being reported?▼

Every runtime claim goes to an independent refuter that must reproduce it by execution, such as a failing test or race run; unreproduced claims are dropped. Quality claims must cite a guideline or consistent practice at a specific line to survive.

What happens if the audit command times out mid-run?▼

The round runs in its own process, so a timeout stops only the wait, not the round. Use clerk audit wait to block until it lands, clerk audit status to check liveness, or re-run clerk audit run to resume from the recorded phase.

When should I not use a full multi-agent audit?▼

Skip it for tiny diffs like a two-line change, since a round spawns 10-20 agents over 15-25 minutes. Also fix a red test suite first, because lenses assume the suite passes and auditing broken work wastes the pass.