skills.rest
AIKAGRYA
AIKAGRYAOFFICIAL
Explore all skills by this author →
GitHub

dharma-preflight-review

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

1|3|Updated Mar 9, 2026
Search Tags:#code review#test gaps#pre-merge#release readiness#trust boundaries#severity findings#ship blockers
One-click install
npx skills add https://github.com/AIKAGRYA/dharma_swarm --skill dharma-preflight-review-aikagrya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dharma-preflight-review
Source: https://github.com/AIKAGRYA/dharma_swarm/tree/main/mode_pack/claude/preflight-review
Command: npx skills add https://github.com/AIKAGRYA/dharma_swarm --skill dharma-preflight-review-aikagrya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before merging or releasing, teams need a final check that catches critical risks rather than style nitpicks. This Skill performs a pre-landing review focused on structural bugs, silent failures, trust boundaries, and missing tests, so ship blockers surface before production. ## Core Features & Use Cases - Severity-Ordered Findings: Produces a findings-first report ordered by severity, covering structural bugs and silent failures. - Trust-Boundary Analysis: Examines trust boundaries and identifies test gaps that could hide production failures. - Ship Blocker Detection: Explicitly flags blockers and refuses to treat a branch as ready when a critical issue exists. - Use Case: A developer finishes a feature branch and asks for a pre-merge review; the Skill returns findings by severity, trust-boundary notes, test gaps, and ship blockers, then hands off to shipping or QA modes if clear. ## Quick Start Review this branch before merge and report any structural bugs, trust-boundary risks, test gaps, and ship blockers ordered by severity.

Frequently Asked Questions about dharma-preflight-review

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

FAQPage Schema
How do I review code for ship blockers before merging?▼

Run a preflight review that focuses on structural bugs, silent failures, trust boundaries, and missing tests rather than style. The output lists findings by severity and explicitly flags ship blockers so a risky branch is never treated as ready.

What should a pre-merge code review focus on?▼

A pre-merge review should prioritize critical risks: structural bugs, silent failures, trust-boundary violations, and test gaps. Style-only feedback is intentionally excluded so attention stays on what can hurt production.

How are preflight review findings structured?▼

Findings come first, ordered by severity, followed by trust-boundary notes, test gaps, and ship blockers. If there are no findings, the review states that explicitly instead of padding the report.

When should I not use a preflight review mode?▼

Do not use it for early-stage design feedback or style and formatting checks, since it ignores style-only issues. It is meant for code or plans that are nearly ready and need a final risk assessment before merge or release.

What happens after a preflight review passes?▼

If the review is clear of blockers, the workflow hands off to shipping or QA modes such as dharma-ship or dharma-qa. If a critical blocker exists, the branch is explicitly not treated as ready.

Related Skills

Explore More Software Engineering Skills→
vorynkavitaliyvorynkavitaliy

finishing-a-development-branch

Guide merge or cleanup decisions after tests pass on a development branch.

Community
Advanced
MichaelSolatiMichaelSolati

team-qa

Orchestrate game QA cycles with test planning, execution, and sign-off reports.

Community
Advanced
shakhovskiya-createshakhovskiya-create

tooling-python

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

Community
Advanced
nassimbfnassimbf
3

requesting-code-review

Dispatch a code-reviewer subagent to generate structured feedback for pre-merge checks.

Community
Intermediate