Skill Claude CodeCodex
Break a feature spec into intentional waves and bite-sized tasks grouped by dependency. Use after a spec is written to prepare for easy-to-track implementation.
3 16d ago A 34 tokens
3Stars on the repository
20Mods indexed here, across every type
16d agoLast push, which is what freshness is scored on
noneNo LICENSE: all rights reserved, so bodies are not copied
Skill Claude CodeCodex
Audit a codebase for dead code, unreachable branches, duplicated logic, and vestigial abstractions, then remove them safely with proof. Use to reduce sprawl, pay down tech debt, or clean up after a feature is retired or migrated.
3 16d ago A 57 tokens
Skill Claude CodeCodex
Review a code change (diff or PR) for ship-readiness before merge. Use when reviewing your own or someone else's changes prior to committing/merging/etc.
3 16d ago A 38 tokens
gjalla-debug
04Skill Claude CodeCodex
Investigate a reported problem down to its root cause, with evidence, before proposing a fix. Use when something is broken, behaving unexpectedly, or a user reports an issue you can't immediately explain.
3 16d ago A 43 tokens
Skill Claude CodeCodex
Make sure your code is ready to commit, then stage changes into clean, atomic commit. Use before committing.
3 16d ago A 30 tokens
Skill Claude CodeCodex
Full review of a plan or spec to be sure there are no surprises, gaps, or mistakes. Use to harden a spec before implementation.
3 16d ago A 34 tokens
gjalla-spec
07Skill Claude CodeCodex
Create a well-thought-out plan covering problem statement, goals, technical approach, and verification criteria. Use while planning / before implementing any non-trivial feature.
3 16d ago A 36 tokens
Skill Claude CodeCodex
Audit a test suite to find tests that give false confidence — tests that encode bugs, duplicate coverage, or are so heavily mocked they can't catch real regressions. Use to improve robustness, audit coverage, or harden a risky area.
3 16d ago A 53 tokens