skills.rest
AmitabhainArunachala
AmitabhainArunachalaCOMMUNITY
Explore all skills by this author →
GitHub

dharma-preflight-review

Reviews near-ready code for structural bugs, trust boundaries, and ship blockers.

Updated Aug 5, 2026
Search Tags:#code review#preflight#test gaps#release readiness#trust boundaries#severity findings#ship blockers
One-click install
npx skills add https://github.com/AmitabhainArunachala/dharma_swarmv.01 --skill dharma-preflight-review-amitabhainarunachala
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dharma-preflight-review
Source: https://github.com/AmitabhainArunachala/dharma_swarmv.01/tree/main/mode_pack/claude/preflight-review
Command: npx skills add https://github.com/AmitabhainArunachala/dharma_swarmv.01 --skill dharma-preflight-review-amitabhainarunachala

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often merge or release code that still hides structural bugs, silent failures, and untested trust boundaries. This Skill performs a focused pre-landing review that surfaces what can still hurt you in production before you ship. ## Core Features & Use Cases - Severity-Ordered Findings: Produces a findings-first report ordered by severity, covering structural bugs, silent failures, and missing tests. - Trust-Boundary Analysis: Explicitly documents trust-boundary notes and test gaps alongside ship blockers. - Clear Handoff: When the review is clean, it hands off to dharma-ship or dharma-qa; when a critical blocker exists, it refuses to treat the branch as ready. - Use Case: Before merging a large feature branch, run this review to get a severity-ranked list of remaining risks and an explicit go/no-go signal. ## Quick Start Ask the assistant to run a preflight review on the current branch and report findings by severity, trust-boundary notes, test gaps, and ship blockers.

Frequently Asked Questions about dharma-preflight-review

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

FAQPage Schema
How do I run a pre-merge code review for ship blockers?▼

Invoke this review mode on code that is nearly ready to land. It returns findings ordered by severity, trust-boundary notes, test gaps, and ship blockers, so you can decide whether the branch is ready to merge.

What does a preflight code review check before release?▼

It checks for structural bugs, silent failures, trust-boundary violations, and missing tests. Style-only feedback is explicitly excluded so the review stays focused on production risk.

When should I use a preflight review instead of a general code review?▼

Use it when the code or plan is nearly ready and you need to know what can still hurt you in production. It is a final risk gate before merge or release, not a substitute for ongoing design or style review.

What happens if the preflight review finds a critical blocker?▼

The review reports the blocker as a ship blocker and does not treat the branch as ready. Only when the review is clear does it hand off to dharma-ship or dharma-qa for the next step.

What are the limitations of this preflight review mode?▼

It deliberately skips style-only feedback and relies on read, search, and shell tools rather than executing the code. It identifies risks and test gaps but does not fix them or run the test suite itself.

Related Skills

Explore More Software Engineering Skills→
spiriMirrorspiriMirror
307

fix-pr

Fix GitHub PR review feedback by implementing, testing, and pushing changes.

Official
Intermediate
ceratops-codeceratops-code

ceratops-gh-codex-skill-ship

Ship staged Ceratops skill batches from runtime checkout to GitHub and restore main.

Official
Intermediate
shakhovskiya-createshakhovskiya-create

tooling-python

Run Ruff, MyPy, Bandit, Pip-audit, Radon, Vulture, and Mutmut audits on Python projects.

Community
Advanced
udecodeudecode
1.2k

reviewing-pr

Automate GitHub pull request reviews with severity-rated feedback.

Official
Intermediate