When the user pastes a specific error (stack trace, build failure,
"failed to execute X"), Claude now follows the error directly to the
relevant files instead of exploring the whole codebase.
https://claude.ai/code/session_01Fzv8baXnEVVhnrffAb3Ucc
Instead of a CLI the user runs separately, this is now two files you
drop into any repo:
- CLAUDE.md: read automatically by Claude Code, teaches it to scan
first, commit often, and leave handoff notes when usage runs low
- scan.py: standalone script Claude runs itself to find errors via
linters/tests/type-checkers, using zero AI tokens
No workflow change for the user — they type in Claude Code as before.
https://claude.ai/code/session_01Fzv8baXnEVVhnrffAb3Ucc
- ctc scan: runs linters/tests/type-checkers to find errors without
burning AI tokens. Auto-detects Python, Node, Rust, Go projects.
- ctc init: drops a CLAUDE.md into any repo teaching Claude Code to
work efficiently (chunk work, commit often, read scan results first).
- Updated README with the actual workflow: scan -> paste -> fix.
https://claude.ai/code/session_01Fzv8baXnEVVhnrffAb3Ucc
CLI tool that decomposes big coding tasks into self-contained chunks,
each with a ready-to-paste prompt including codebase context, targeted
instructions, and dependency tracking. Supports phase, component, and
manual decomposition strategies.
https://claude.ai/code/session_01Fzv8baXnEVVhnrffAb3Ucc
Claude