From armory
Runs a gate-oriented safety audit on code changes before they land, using a two-pass checklist to triage critical (blocking) and informational issues. Triggers on phrases like "is this safe to land" or "/pre-landing-review".
How this skill is triggered — by the user, by Claude, or both
Slash command
/armory:pre-landing-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Gate-oriented safety audit for code changes before landing. Uses a structured checklist with two-pass severity triage and blocking/non-blocking classification.
Gate-oriented safety audit for code changes before landing. Uses a structured checklist with two-pass severity triage and blocking/non-blocking classification.
Distinct from pr-review: pr-review is a multi-dimension code quality review. This skill is a gate-oriented safety audit — it uses an external checklist with two-pass severity triage and a blocking/non-blocking classification.
Native alternative: Claude Code's
/ultrareviewruns a dedicated native review session optimized for bug-finding (Anthropic ships three free per month on Pro/Max plans at Opus 4.7's launch). Use this skill for checklist-driven, gate-oriented blocking classification with a documented triage protocol; use/ultrareviewfor lightweight bug-hunting on a single change.
Identify the changes to review:
git symbolic-ref refs/remotes/origin/HEAD)Read references/checklist.md. This is mandatory — if the checklist is unreadable, STOP and report the error.
Review the diff against critical safety categories. These are potential ship-blockers.
For each CRITICAL finding:
AskUserQuestion with exactly three options: Fix now / Acknowledge risk / False positiveReview against remaining categories:
Conditional Side Effects — side effects hidden in conditional branches, callbacks triggered by state changes, error handlers silently swallowing failures.
Magic Numbers — unexplained numeric literals, hardcoded thresholds without constants, timeout values without rationale.
Dead Code — unreachable branches, unused imports, commented-out code without explanation.
Test Gaps — new code paths without test coverage, modified behavior without updated tests, missing edge case and error path tests.
Crypto & Entropy — weak random sources for security contexts, hardcoded secrets, missing TLS/encryption for sensitive data in transit.
Time Window Safety — timezone-naive comparisons, daylight saving edge cases, cron expressions not accounting for clock skew.
Type Coercion — implicit type conversions that could lose data, numeric precision loss across boundaries, implicit string encoding at I/O boundaries.
Present all informational findings in a single summary table (file, line, category, description).
Do NOT flag:
Gate verdict (CLEAR TO LAND / BLOCKED), critical issues summary with resolution status, informational findings table.
This skill is read-only by default — only modifies code when user explicitly chooses "Fix now" on a critical issue.
npx claudepluginhub mathews-tom/armory --plugin armoryPerforms structured code reviews checking requirements, quality, and security standards after changes or before merge. Uses git diffs, context snapshots, and blast radius for scope.
Reviews code changes for correctness, readability, architecture, security, and performance. Checks lint, type safety, test coverage, and security issues. Use for PRs, audits, or pre-merge reviews.
Reviews and verifies code before merge via triage-first checks (up to 16 parallel agents). Pipeline mode verifies vs plans; general mode for PRs/branches/staged changes. Flags findings only.