Skill Claude CodeCodex
Conservative dependency edges between work items — declare that A blocks B only when B clearly consumes A’s output or cannot start until A is done. Use when ordering decomposition parts, proposing blocked-by relations across a backlog, or explaining why two items should (or should not) serialize. Never invent keys or…
Skill Claude CodeCodex
Commit and pull-request discipline — one intent per PR, honest scoped commits, reviewable descriptions, no force-push of shared branches, no tooling junk in the tree. Use when committing work, opening or updating a pull/merge request, or writing a PR description. Companion: verification-before-completion before you…
Skill Claude CodeCodex
Four-phase root-cause debugging — investigate, pattern-match, hypothesize, then fix. Use when facing a bug, test failure, build break, unexpected behavior, or flaky path, before proposing or shipping a fix. Forbids symptom patches without a causal chain. Companion: verification-before-completion for proof after the…
Skill Claude CodeCodex
Strict red-green-refactor discipline at public seams — write a failing test, watch it fail, write minimal code to pass. Use when implementing features, bug fixes with a known reproduction, or new modules, before production code. Prefer port/fakes over private-helper tests. Companion: verification-before-completion for…
Skill Claude CodeCodex
Evidence before success claims — identify the proof command, run it fresh, read exit codes and output, then claim only what the evidence supports. Use before marking work done, fixed, or passing; before commit or PR; whenever tempted to assert status from build alone. Companion: test-driven-development for…