signoff

Runs independent adversarial review of freshly built code slices and issues a signed verdict.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/line7works/tony-skills --skill signoff-line7works
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: signoff
Source: https://github.com/line7works/tony-skills/tree/main/plugins/signoff/skills/signoff
Command: npx skills add https://github.com/line7works/tony-skills --skill signoff-line7works

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code written by an AI session cannot be trusted to review itself, and rubber-stamp approvals let defects ship. This Skill brings in fresh reviewers who did not write the code, mandates them to find reasons to reject, and produces an honest signed verdict before a slice counts as done. ## Core Features & Use Cases - Independent multi-lens review: Spawns fresh subagent reviewers with distinct lenses (spec, correctness, seams, plus security and tests at DEEP depth) that read the source themselves and report findings with file:line evidence. - Severity-graded verdicts: Classifies findings as BLOCKER, MAJOR, or MINOR and issues SIGNED OFF, SIGNED OFF WITH CONDITIONS, or REJECTED verdicts, with a sweep that re-verifies open items from prior slices. - Repo-specific inspection sheets: Reads a per-repo REVIEW.md to toggle review passes (correctness, security, accessibility, data-safety) and apply custom severity bars and repo-specific checks. - Use Case: After building a feature slice against a blueprint doc, ask for a sign-off; the Skill detects the changed files, grades them against the slice's acceptance criteria, runs the tests, and returns a verdict with a punch list. ## Quick Start Ask the assistant to sign off on the slice that was just built so independent reviewers inspect it against the build doc and return a verdict.

Frequently Asked Questions about signoff

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

FAQPage Schema
How do I get an adversarial code review of work an AI just built?

Ask for a sign-off after a slice is built. The Skill detects the uncommitted changes plus branch commits, spawns fresh reviewer subagents with spec, correctness, and seams lenses, and returns a signed verdict with evidence-backed findings.

What is the difference between LIGHT, LEAN, and DEEP review depths?

LIGHT uses one reviewer with a fused spec and correctness lens for small diffs. LEAN runs three parallel reviewers (spec, correctness, seams) by default. DEEP adds security and tests lenses, and is required when the slice touches auth, money, or user data.

Can I customize which checks the code review runs per repository?

Yes. A REVIEW.md file at the repo root toggles passes (correctness, security, accessibility, data-safety), defines a custom severity bar, and lists repo-specific checks. On first run the Skill proposes a REVIEW.md inferred from the repo and asks before writing it.

Why does the sign-off review refuse to run on some sessions?

Reviewers must run at Opus-class models or better. If the session is below that floor, the Skill stops and only offers a lightweight review explicitly labeled as not a sign-off, with no verdict line.

What happens to open findings from a previous rejected slice?

A built-in sweep brings still-open BLOCKER and MAJOR items from prior slices into the new reviewers' scope. Verified fixes are recorded in a recheck-format ledger block, and full clearance flips the prior card to signed off.

Does the sign-off skill fix the defects it finds?

No. It reports findings and a verdict only; fixing is a separate instruction the user gives afterward. The only files it writes are the verdict record and REVIEW.md, and only with the user's approval.