fixing-code
Fix All Issues
Execute until clean. Parallel analysis, sequential fixes.
Parse $ARGUMENTS:
investigate→ 5-Why root cause analysis before fixing (for recurring or mysterious bugs)team→ Agent team mode: Analysts compete to find root causes and debate solutions
Use TodoWrite to track these 6 phases:
- Run validation
- Parallel analysis (spawn agents or team)
2a. 5-Why investigation (if
investigate) - Collect analysis results
- Sequential fixes
- Final verification
More from alexei-led/claude-code-config
brainstorming-ideas
Turn ideas into designs through collaborative dialogue. Use when user wants to brainstorm, design features, explore approaches, or think through implementation before coding.
19refactoring-code
Batch refactoring via MorphLLM edit_file. Use for "refactor across files", "batch rename", "update pattern everywhere", large files (500+ lines), or 5+ edits in same file.
11testing-e2e
E2E testing with Playwright MCP for browser automation, test generation, and UI testing. Use when discussing E2E tests, Playwright, browser testing, UI automation, visual testing, or accessibility testing. Supports TypeScript tests and Go/HTMX web applications.
10writing-python
Idiomatic Python 3.14+ development. Use when writing Python code, CLI tools, scripts, or services. Emphasizes stdlib, type hints, uv/ruff toolchain, and minimal dependencies.
7looking-up-docs
Library documentation via Context7. Use for API references, code examples, framework docs.
7writing-typescript
Idiomatic TypeScript development. Use when writing TypeScript code, Node.js services, React apps, or discussing TS patterns. Emphasizes strict typing, composition, and modern tooling (bun/vite).
7