bugfix
01stateofthehart/claude-code-config
Command
You are debugging a bug. Follow this sequence exactly. Do NOT skip steps.
2 4mo ago A 0 tokens
debug
02stateofthehart/claude-code-config
Command
You are debugging an issue where the cause is unknown. This is different from /bugfix — here you don't know what's wrong yet. Follow this sequence.
2 4mo ago A 0 tokens
implement
03stateofthehart/claude-code-config
Command
You are implementing a feature. Follow this sequence. Do NOT start writing code until Step 3.
2 4mo ago A 0 tokens
prune-list
04stateofthehart/claude-code-config
Command
List all Claude Code sessions with their sizes. Run.
2 4mo ago A 0 tokens
prune
05stateofthehart/claude-code-config
Command
Run the session pruner. If the user passed no arguments (i.e. $ARGUMENTS is empty), run.
2 4mo ago A 0 tokens
refactor
06stateofthehart/claude-code-config
Command
You are refactoring code. The goal is to improve structure WITHOUT changing behavior. Follow this sequence.
2 4mo ago A 0 tokens
review
07stateofthehart/claude-code-config
Command
You are reviewing code. Use a subagent with fresh eyes — do NOT review in the same context you wrote the code. If you wrote the code in this session, spawn an independent reviewer subagent.
2 4mo ago A 0 tokens
test
08stateofthehart/claude-code-config
Command
You are writing tests for existing code. The goal is to catch real bugs, not achieve coverage metrics.
2 4mo ago A 0 tokens
stateofthehart/claude-code-config
Skill Claude CodeCodex
This skill should be used when the conversation is getting long, context feels bloated, Claude mentions compaction or context limits, the user asks about "context", "pruning", "memory", "compaction", or when Claude notices tool outputs are very large. Also activate when resuming a session, starting a large task, or…
2 4mo ago A 86 tokens