Cc
Run a full code check cycle and fix all issues until clean.
Claude CodeGeneric
Run a full code check cycle and fix all issues until clean.
## Steps
1. Run all three checks in order:
- `ruff check . --fix` — linting (auto-fix what's safe)
- `ruff format .` — formatting
- `mypy --strict` — type checking (no auto-fix, manual only)
2. Address any remaining issues:
- Fix ruff violations that weren't auto-fixed
- Fix mypy errors by correcting type annotations, signatures, or logic as needed
- Do not suppress errors with `# type: ignore` or `noqa` unless the error is a known false positive in a third-party library
3. Re-run all checks. Repeat until fully clean.
## Escalate to the human instead of fixing when:
- A type error requires changing a function signature called in multiple places
- A type error points to an architectural mismatch (e.g. wrong-level responsibility, incompatible abstractions)
- A linting violation conflicts with an established pattern elsewhere in the codebase
- A fix would require changes outside the scope of the recent edit
- You've cycled more than 3 times without getting clean — something systemic is wrong
## Report format when escalating
State clearly:
- Which check is failing and the exact error
- Why you cannot fix it locally
- What the likely root cause is
- What decision or change is needed from the human
Maintain Cc?
Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.
[Cc on getagentictools](https://getagentictools.com/loops/mlinnem-cc?ref=badge)