Agent skill · pedronauck
impl-peer-review
Cross-LLM peer review of an implemented change (the diff) via `compozy exec`: an independent reviewer runtime pressure-tests the diff and writes one scoped Markdown findings artifact for user-directed remediation. Project-agnostic — any repo or language; auto-discovers project rule files and the verify command. Use after an implementation pass (feature, bug fix, refactor) when the user explicitly asks for an external review of the diff before commit or PR. Do not use for spec/TechSpec review — use spec-peer-review.
What it needs
About 7k tokens when loaded.
What this skill does
Implementation Peer Review An independent reviewer runtime pressure-tests an implementation diff. This skill runs that cross-LLM review only on explicit user request after an implementation pass; its scope is the diff plus any --context files the user names, decoupled from any task-tracking system. Compozy is the review engine: each round is one compozy exec against a configurable runtime. The findings file the reviewer writes is the sole source of truth — treat compozy exec stdout/stderr and the event log as operational evidence only. Bundled files Resolve every scripts/<name> or references/<name> path relative to this SKILL.md's directory (<skill-dir>). All bundled files are read-only — read or run them, never edit them during a round. Asking the user When a step tells you to ask the user (which findings to incorporate, whether to run another round), use the runtime's interactive question tool — the one that presents a question and pauses until the user answers (e.g. AskUserQuestion). If the runtime has no such tool, present the question as the complete assistant message and stop; answer it yourself only after the user replies. Inputs All inputs are optional. Defaults make the common path impl-peer-review with no arguments. --files <p1,p2,...> — scope the review to explicit paths instead of the full branch diff. --context <p1,p2,...> — additional context files to feed the reviewer (a spec, ADR, design doc, RFC, README). The skill never assumes any of these exist. --base <git-ref> — base ref for the diff. Defaults to main. Use --base HEAD~N for a narrower scope. --staged — review staged changes only (git diff --staged) instead of a branch diff. --out <dir> — output directory for round artifacts. See Output Directory. --verify <cmd> — the verification command (build/tests) used as both the readiness gate and the post-remediation gate. When omitted, auto-detect per references/readiness-checks.md; if none resolves, ask the user. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills pedronauck/impl-peer-review--defaa2