ln-12-delivery-reviewer
Reviews a completed scoped change and its affected runtime and contract paths. Use to find change-caused defects and verify readiness; not for codebase audit, implementation, or repair.
npx skills add levnikolaevich/claude-code-skills --skill ln-12-delivery-reviewer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Reviews a completed scoped change and its affected runtime and contract paths. Use to find change-caused defects and verify readiness; not for codebase audit, implementation, or repair.
How it works
- Treat the ordered checkbox workflow as the Definition of Done and work through every item in order.
- Mark each item complete only when action and required evidence are complete; otherwise leave incomplete and provide specified notes.
- Before returning, apply verdict rules to every incomplete item and prepend a Checklist line indicating completion status and next actions.
- Use a structured tool-routing scheme to gather evidence: read repository state, inspect diffs, verify definitions and consumers, run automated verification if available, observe behavior, perform correction research if needed, and conduct an independent review with limited subagents.
- For each evidence question, rely on reproduced behavior, changed code paths, acceptance criteria, and official contracts as the strongest proof; document evidence and impact for each finding.
- Include an Independent Review Panel approach where lenses (specialist viewpoints) are selected to inform the verdict; limit rounds and subagents per the two-round budget.
When to use it
• When evaluating a completed scoped change to determine if it meets acceptance and release safety criteria. • When verifying the causal paths from change to business outcome and ensuring no unrelated code is implicated.
What it can touch
- Tools: claude-code, codex
- States: reads repository state, diffs, citations to definitions and consumers, and evidence artifacts
Caveats
- This skill explicitly avoids auditing unrelated code, implementing repairs, or widening scope beyond the requested delivery change.
- It requires confirming that evidence supports acceptance criteria and that the path from change to outcome is properly evidenced; otherwise items remain incomplete.
# Delivery Reviewer **Goal:** Review only the requested delivery change and the causal paths needed to prove its business outcome. Judge scoped acceptance and release safety with concise evidence; do not audit unrelated code, repair findings, update trackers, or widen scope. **Execution contract:** Treat the ordered checkbox workflow below as this skill's Definition of Done. Work through every item in order, and mark it complete only when its action and required evidence are complete. `N/A`, skipped, unavailable, or delegated items remain incomplete. Before returning, apply this skill's verdict, decision, and approval rules to every incomplete item and prepend **Checklist: X/Y complete**<br>**Incomplete: None | section/item — reason; outcome impact; exact next action**; list every incomplete item. ## Tool Routing | Need | Preferred capability | Use when | Fallback | |---|---|---|---| | Scope and repository state | Native file reads plus Git | Establishing outcome, non-goals, base, head, and worktree | Supplied requirements with explicit limitations | | Changed behavior | Diff, status, and focused reads | Resolving the implementation delta and entrypoints | Compare supplied artifact
- Tool Routing
- Evidence Rules
- Independent Review Panel
- Checklist
- 1. Establish Business and Change Scope
- 2. Trace Requirements into Implementation
- 3. Review Safety, Contracts, and Simplicity
- 4. Verify Tests, Documentation, and Operations
- 5. Challenge and Synthesize
- Output Contract
What does the ln-12-delivery-reviewer skill do?
Reviews a completed scoped change and its affected runtime and contract paths. Use to find change-caused defects and verify readiness; not for codebase audit, implementation, or repair.
How do I install it?
Run `npx skills add levnikolaevich/claude-code-skills --skill ln-12-delivery-reviewer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From levnikolaevich/claude-code-skills, a repository with 528 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.