bugfix
01stateofthehart/claude-code-config
Command Claude Code
You are debugging a bug. Follow this sequence exactly. Do NOT skip steps.
not rated 2 6mo ago A 0 tokens
2Stars on the repository
9Mods indexed here, across every type
6mo agoLast push, which is what freshness is scored on
noneNo LICENSE: all rights reserved, so bodies are not copied
debug
02stateofthehart/claude-code-config
Command Claude Code
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.
not rated 2 6mo ago A 0 tokens
implement
03stateofthehart/claude-code-config
Command Claude Code
You are implementing a feature. Follow this sequence. Do NOT start writing code until Step 3.
not rated 2 6mo ago A 0 tokens
prune-list
04stateofthehart/claude-code-config
Command Claude Code
List all Claude Code sessions with their sizes. Run.
not rated 2 6mo ago A 0 tokens
prune
05stateofthehart/claude-code-config
Command Claude Code
Run the session pruner. If the user passed no arguments (i.e. $ARGUMENTS is empty), run.
not rated 2 6mo ago A 0 tokens
refactor
06stateofthehart/claude-code-config
Command Claude Code
You are refactoring code. The goal is to improve structure WITHOUT changing behavior. Follow this sequence.
not rated 2 6mo ago A 0 tokens
review
07stateofthehart/claude-code-config
Command Claude Code
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.
not rated 2 6mo ago A 0 tokens
test
08stateofthehart/claude-code-config
Command Claude Code
You are writing tests for existing code. The goal is to catch real bugs, not achieve coverage metrics.
not rated 2 6mo ago A 0 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: