destrier

Report weekly throughput and cycle-time metrics for one or more GitHub repos.

Initialize today's knowledgebase session summary (an OKF v0.1 bundle) in the current repo and show the last 3 summaries.

Install destrier's critical-path pre-commit guard into the current git repo.

Security-review the pending changes — de-identification + secret scan, plus roborev security review when available.

Bootstrap destrier's external tools — build gitnexus from git and install roborev via its official installer.

Use this skill for ANY debugging task — a failing test, a production error, a crash, a 500/409/timeout, or any behavior that surprises you — and ESPECIALLY when a previous fix did not hold, when something works in one environment but fails in another, when a bug cannot be reproduced, or when you catch yourself guessing or assuming the cause instead of observing it (phrases like "works locally but fails in prod", "I think it's", "it must be", "can't reproduce", "fixed it but it came back", "why is this happening", "the code looks right but"). It installs evidence-over-deduction habits: capture ground truth at the boundary instead of inferring it from downstream state, isolate the one differing variable when two "identical" cases diverge, trace a symptom to its true layer (often a code-versus-config contradiction far from where the error surfaces), match the reproduction to the real scenario, and verify the fix against the original failure. Apply it even for seemingly simple bugs and even when you think you already know the cause — that is exactly when wrong fixes happen; pair it with whatever structured debugging loop you use. Do NOT use it for building new features, refactors or renames, performance tuning of already-correct code, code review, or "explain how X works" questions.

Use at the start and end of any work session to maintain a durable, model-labeled knowledgebase in the Open Knowledge Format (OKF). At start, read the last few session summaries for continuity; during work, append dated deltas and promote durable knowledge into cross-linked concept files; at end, update the indexes. Use when resuming work, handing off between sessions or agents, or when the user mentions a knowledgebase, session summary, handover, or OKF.

Use when authoring a project constitution or a feature specification under Spec-Driven Development (spec-kit) — i.e. before running /speckit-constitution or /speckit-specify. Makes collaborative brainstorming the front-end for those commands: brainstorm the intent, distill it to a short input brief, hand that to the speckit command, and continue the speckit loop — instead of writing a separate design doc and invoking writing-plans. Triggers on "write the constitution", "spec out this feature", "start a new feature under SDD", or any move toward /speckit-constitution / /speckit-specify.

2 hooks across 2 events