Skill Claude CodeCodex
A preparation process that loads relevant project guidance and chooses how deeply to inspect the code before making changes.
20 1mo ago A 56 tokens
original MIT
20Stars on the repository
16Mods indexed here, across every type
1mo agoLast push, which is what freshness is scored on
MITLicence, which decides whether bodies are shown
Skill Claude CodeCodex
Use when starting creative work - creating features, building components, adding functionality, or modifying behavior - before any implementation. Explores user intent, requirements and design.
20 1mo ago A 36 tokens
copy · 80% MIT
Skill Claude CodeCodex
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.
20 1mo ago A 38 tokens
original MIT
spec-steward
04Skill Claude CodeCodex
A repository-maintenance procedure for organizing the .spec knowledge base. It covers rules, standards, feature records, agents, and reusable skills, including their required names and metadata.
20 1mo ago A 72 tokens
original MIT
Skill Claude CodeCodex
Use when executing implementation plans with independent tasks in the current session.
20 1mo ago A 17 tokens
original MIT
Skill Claude CodeCodex
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
20 1mo ago A 21 tokens
original MIT
Skill Claude CodeCodex
A task-planning workflow that breaks a large or unclear development goal into smaller task cards. Each card describes its scope, dependencies, and objectively checkable acceptance conditions.
20 1mo ago A 79 tokens
original MIT
Skill Claude CodeCodex
Use when implementing any feature or bugfix, before writing implementation code.
20 1mo ago A 17 tokens
copy · 83% MIT
Skill Claude CodeCodex
Use when starting feature work that needs isolation from current workspace, and when implementation is complete and you need to integrate the work - covers creating isolated workspaces (native tools or git worktree fallback) and finishing branches (verify, merge/PR, cleanup).
20 1mo ago A 57 tokens
original MIT
Skill Claude CodeCodex
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always.
20 1mo ago A 43 tokens
original MIT
Skill Claude CodeCodex
Use when you have a spec or requirements for a multi-step task, before touching code.
20 1mo ago A 21 tokens
original MIT