Caveman debug logging plugin¶
- Date: 2026-04-21
- Status: Accepted
- Tags:
tooling
Context¶
Debugging unfamiliar codebases often requires quick visibility into runtime state. Setting up a full debugger for every language and framework is time-consuming, especially during exploratory work. Printf-debugging is effective but tedious — inserting and cleaning up log statements manually is error-prone and slows down the feedback loop.
Decision¶
Install the caveman plugin from claude-plugins-official on the work laptop. It injects console.log/print statements for quick instrumentation and cleans them up afterward. Available as a Claude Code tool for on-demand debug logging.
Alternatives Considered¶
| Option | Why Rejected |
|---|---|
| Manual printf-debugging | Works but tedious; easy to forget cleanup |
| Language-specific debugger setup per project | Too much setup overhead for exploratory work across multiple repos |
| VS Code debug configurations | Not available in terminal-only Claude Code sessions |
Consequences¶
Positive:
- Fast instrumentation without debugger setup
- Automatic cleanup of debug statements
Negative / Trade-offs:
- Risk of accidentally committing debug statements if cleanup is skipped
- Plugin must be validated from the work laptop environment
Ongoing obligations:
- ✅ Validated 2026-04-21 — caveman mode active and functional on work laptop (caveman:caveman, caveman:compress, caveman:caveman-commit, caveman:caveman-review skills all present)