absolute-debt
Lint and typecheck debt paydown: clear pre-existing repo-wide lint/type violations and suppressions (@ts-ignore, # type: ignore) one rule per wave, fixing causes not symptoms. Runs on green main. For diff-scoped quality use absolute-simplify. Triggers on "absolute debt", "fix our
#workflow #typescript
Install
npx skills add https://github.com/dhruvjainin/absolute/tree/main/skills/absolute-debt
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install dhruvjainin-absolute@llmmart
git clone https://github.com/dhruvjainin/absolute.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole dhruvjainin/absolute collection as a plugin from our marketplace. Git is the plain clone.
README
absolute-debt
Lint and typecheck debt paydown. Clears pre-existing repo-wide lint/type violations and suppressions (@ts-ignore, # type: ignore) one rule per wave, fixing causes not symptoms — never quieting the checker.
Quick Facts
| Field | Value |
|---|---|
| Category | workflow |
| Version | 0.5.0 |
| Platforms | claude-code, gemini-cli, openai-codex, mcp |
| License | MIT |
How to Install
npx skills add maddhruv/absolute-debt
Usage
/absolute-debt "Clear our lint warnings and type errors"
/absolute-debt "Get to strict TypeScript mode"
Runs on green main. For diff-scoped quality use /absolute-simplify.
Maintainers
Skill manifest
Start your first response with the 🧾 emoji.
Absolute Debt
Pay down accumulated lint and type-checker debt across the repo — existing warnings,
errors, and suppressions that built up over time — in safe waves, by rule, with tests green
after each. The goal is a genuinely clean lint + typecheck, not a quieter one.
Runs the shared engine in references/health-engine.md — read it for the
DETECT → SCAN → TRIAGE → FIX → VERIFY → REPORT loop and the safety contract. This file
covers only what's specific to lint/type debt.
When to use
- "Fix our lint warnings", "clean up the type errors", "get the codebase to strict mode".
- Tightening config (enable a rule, raise
tsconfigstrictness) and clearing the fallout. - Burning down accumulated
eslint-disable/@ts-ignore/# type: ignoresuppressions.
debt vs simplify: simplify improves your working diff's quality. debt clears
pre-existing repo-wide lint/type violations on green main. Use debt for standing
cleanup, not for changes you're actively making.
What it scans
| Ecosystem | Lint debt | Type debt |
|---|---|---|
| JS/TS | eslint . (full report, by rule) |
tsc --noEmit |
| Python | ruff check / flake8 |
mypy / pyright |
| Go | golangci-lint run |
go vet ./..., staticcheck |
Also inventory suppressions as debt in their own right: eslint-disable*,
@ts-ignore/@ts-expect-error, # type: ignore, # noqa, //nolint. Each is a hidden
violation. Count violations grouped by rule (not by file) — that's how you wave them.
Risk ranking (TRIAGE)
| Wave | Class | Default |
|---|---|---|
| 1 | autofixable lint (eslint --fix, ruff --fix, gofmt) |
fix now — mechanical, safe |
| 2 | manual lint by rule, low behavioral risk (unused, style, imports) | fix this pass, one rule at a time |
| 3 | type errors, and lint rules that can change behavior if "fixed" wrong | gated — review each, may need real logic |
| 4 | removing suppressions (@ts-ignore etc.) |
gated — each may surface a real bug |
Fix one rule across the repo per wave, not one file across all rules — keeps diffs reviewable and regressions bisectable. Config tightening (enable rule / raise strictness) is itself a finding: propose it, then clear what it surfaces.
Fix & verify
- Run the autofixers first (wave 1), commit-ready, then re-scan to see what's truly manual.
- Manual fixes: address the cause, not the symptom. A type error means the types are
wrong somewhere — fix the type, don't cast to
any/add# type: ignore. - Never clear a violation by suppressing it. Removing suppressions is the goal, not a tool.
- After each wave: full test + lint + typecheck + build. The violation count must drop and nothing regress.
Gotchas
- Fixing by suppressing.
@ts-ignoreto clear a type error adds debt. Forbidden here. any/castto win. Silences the checker, keeps the bug. Fix the real type.- One-file-all-rules waves. Mixes concerns, unreviewable. Go one-rule-all-files.
- Autofix without review.
--fixcan change behavior (e.g.prefer-conston a reassigned var via a bug). Run tests after autofix too. - Disabling the rule instead of fixing. Loosening config to hit zero is debt laundering, not paydown.
Companion commands
/absolute simplify— quality of code you're currently changing./absolute prune— many unused-var/import warnings vanish once dead code is pruned./absolute work— if clearing the debt needs real refactoring, hand off.
Files (absolute)
-
references
-
health-engine.md 5.3 KB
Loading…
-
-
README.md 735 B
# absolute-debt Lint and typecheck debt paydown. Clears pre-existing repo-wide lint/type violations and suppressions (@ts-ignore, # type: ignore) one rule per wave, fixing causes not symptoms — never quieting the checker. ## Quick Facts | Field | Value | |-------|-------| | Category | workflow | | Version | 0.5.0 | | Platforms | claude-code, gemini-cli, openai-codex, mcp | | License | MIT | ## How to Install ```bash npx skills add maddhruv/absolute-debt ``` ## Usage ```bash /absolute-debt "Clear our lint warnings and type errors" /absolute-debt "Get to strict TypeScript mode" ``` Runs on green `main`. For diff-scoped quality use `/absolute-simplify`. ## Maintainers - [@dhruvjainin](https://github.com/dhruvjainin) -
SKILL.md 4.2 KB
--- name: absolute-debt version: 0.5.0 description: > Lint and typecheck debt paydown: clear pre-existing repo-wide lint/type violations and suppressions (@ts-ignore, # type: ignore) one rule per wave, fixing causes not symptoms. Runs on green main. For diff-scoped quality use absolute-simplify. Triggers on "absolute debt", "fix our lint warnings", "clear the type errors", "get to strict mode", "burn down suppressions". category: workflow tags: - workflow - maintenance - linting - typescript - debt platforms: - claude-code - gemini-cli - openai-codex - mcp user-invocable: true argument-hint: "[target]" license: MIT maintainers: - github: maddhruv --- > Start your first response with the 🧾 emoji. ## Absolute Debt Pay down accumulated lint and type-checker debt across the repo — existing warnings, errors, and suppressions that built up over time — in safe waves, by rule, with tests green after each. The goal is a genuinely clean `lint` + `typecheck`, not a quieter one. Runs the shared engine in **`references/health-engine.md`** — read it for the DETECT → SCAN → TRIAGE → FIX → VERIFY → REPORT loop and the safety contract. This file covers only what's specific to lint/type debt. --- ## When to use - "Fix our lint warnings", "clean up the type errors", "get the codebase to strict mode". - Tightening config (enable a rule, raise `tsconfig` strictness) and clearing the fallout. - Burning down accumulated `eslint-disable` / `@ts-ignore` / `# type: ignore` suppressions. **`debt` vs `simplify`:** `simplify` improves *your working diff's* quality. `debt` clears **pre-existing repo-wide** lint/type violations on green `main`. Use `debt` for standing cleanup, not for changes you're actively making. --- ## What it scans | Ecosystem | Lint debt | Type debt | |---|---|---| | JS/TS | `eslint .` (full report, by rule) | `tsc --noEmit` | | Python | `ruff check` / `flake8` | `mypy` / `pyright` | | Go | `golangci-lint run` | `go vet ./...`, `staticcheck` | Also inventory **suppressions** as debt in their own right: `eslint-disable*`, `@ts-ignore`/`@ts-expect-error`, `# type: ignore`, `# noqa`, `//nolint`. Each is a hidden violation. Count violations grouped **by rule** (not by file) — that's how you wave them. --- ## Risk ranking (TRIAGE) | Wave | Class | Default | |---|---|---| | 1 | autofixable lint (`eslint --fix`, `ruff --fix`, `gofmt`) | fix now — mechanical, safe | | 2 | manual lint by rule, low behavioral risk (unused, style, imports) | fix this pass, one rule at a time | | 3 | type errors, and lint rules that can change behavior if "fixed" wrong | gated — review each, may need real logic | | 4 | removing suppressions (`@ts-ignore` etc.) | gated — each may surface a real bug | Fix **one rule across the repo per wave**, not one file across all rules — keeps diffs reviewable and regressions bisectable. Config tightening (enable rule / raise strictness) is itself a finding: propose it, then clear what it surfaces. --- ## Fix & verify - Run the autofixers first (wave 1), commit-ready, then re-scan to see what's truly manual. - Manual fixes: address the *cause*, not the symptom. A type error means the types are wrong somewhere — fix the type, don't cast to `any`/add `# type: ignore`. - **Never** clear a violation by suppressing it. Removing suppressions is the *goal*, not a tool. - After each wave: full test + lint + typecheck + build. The violation count must drop and nothing regress. --- ## Gotchas 1. **Fixing by suppressing.** `@ts-ignore` to clear a type error *adds* debt. Forbidden here. 2. **`any` / `cast` to win.** Silences the checker, keeps the bug. Fix the real type. 3. **One-file-all-rules waves.** Mixes concerns, unreviewable. Go one-rule-all-files. 4. **Autofix without review.** `--fix` can change behavior (e.g. `prefer-const` on a reassigned var via a bug). Run tests after autofix too. 5. **Disabling the rule instead of fixing.** Loosening config to hit zero is debt laundering, not paydown. --- ## Companion commands - **`/absolute simplify`** — quality of code you're *currently changing*. - **`/absolute prune`** — many unused-var/import warnings vanish once dead code is pruned. - **`/absolute work`** — if clearing the debt needs real refactoring, hand off.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.