skills.rest
line7works
line7worksOFFICIAL
Explore all skills by this author →
WebsiteGitHub

vertical

Runs whole-build adversarial review with local and outside model reviewers, producing one verified verdict doc.

Updated Jun 2, 2026
Search Tags:#git#code review#adversarial review#multi-model review#build loop#whole-build signoff#verdict doc
One-click install
npx skills add https://github.com/line7works/tony-skills --skill vertical-line7works
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vertical
Source: https://github.com/line7works/tony-skills/tree/main/plugins/vertical/skills/vertical
Command: npx skills add https://github.com/line7works/tony-skills --skill vertical-line7works

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? After every slice of a build is individually signed off, there is no final check that the whole structure holds together against its base commit. This Skill performs that capstone inspection: it gates on all slices being signed off, reviews the entire vertical with fresh local subagent reviewers plus optional outside models (GPT, Gemini, DeepSeek, Qwen), verifies every outside finding against the source, and writes one dated verdict doc. ## Core Features & Use Cases - Hard gate and preconditions: Refuses to run unless every slice stands signed off, the repo is a git repo, and the working tree is clean where the review looks; only the user's explicit invocation can collapse the gate. - Cold outside review with secrets physically absent: Outside reviewers receive a tracked-files-only git archive export (excluding docs/reviews/ and REVIEW.md), the build doc, and the change boundary — never the live working tree, prior verdicts, or chat context. - Verified merge, one verdict doc: Every outside finding is adversarially verified against the source before reaching the verdict; refuted findings are counted (Refuted: N) and quarantined in a raw appendix, and the verdict is appended to docs/reviews/<date>-vertical-<feature>.md. - Use Case: After a multi-slice feature build completes the blueprint → build → signoff → recheck loop, run /vertical to get a final SIGNED OFF / REJECTED verdict on the whole build before shipping. ## Quick Start Say "run the vertical" or "/vertical" on a completed build doc and answer the reviewer-selection prompt to get a verified whole-build verdict doc.

Frequently Asked Questions about vertical

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

FAQPage Schema
How do I run a whole-build review after all slices are signed off?▼

Invoke /vertical naming the build doc once every slice's Status line reads signed off. The skill gates on that state, asks which outside reviewers to include, runs local and outside reviews, and writes one verdict doc under docs/reviews.

What is the difference between signoff and vertical review?▼

Signoff inspects one built slice; vertical inspects the entire build against its base commit after all slices are signed off. Vertical reuses signoff's review mechanics but adds whole-build scope, outside reviewers, and the merge of their findings.

Can outside AI models review my code without seeing secrets?▼

Yes. Outside reviewers receive only a tracked-files-only git archive export with docs/reviews and REVIEW.md excluded, never the live working tree. Untracked, gitignored, and credential files are physically absent from what outside models can read.

Why does the vertical review stop before running?▼

The run stops if any slice is not signed off, the directory is not a git repo, or uncommitted changes touch the change boundary or build doc. It reports exactly which condition failed; only your explicit invocation wording can override the gate.

What happens to findings outside reviewers hallucinate?▼

Every outside finding is adversarially verified against the source before reaching the verdict. Findings that fail verification are dropped from the verdict, counted in a Refuted: N line, and kept only in the raw unverified appendix.

Does the vertical skill fix the issues it finds?▼

No. It stops at the verdict and never modifies code, the build plan, or status cards. Fixing is a separate instruction after you read the verdict doc.

Related Skills

Explore More Software Engineering Skills→
scoots31scoots31

qa-triage

Classifies and routes bugs, missing requirements, and regressions found during QA testing.

Community
Intermediate
mopeyjellyfishmopeyjellyfish
1

commit

Coordinate commit, push, and PR steps with evidence for a branch.

Community
Advanced
assafmanorassafmanor

incremental-implementation

Implements multi-file code changes in thin vertical slices with per-slice testing and commits.

Community
Intermediate
thesammykinsthesammykins

code-quality-gates

Enforces predefined quality gates for code reviews and merges.

Community
Advanced