本文へ移動
cccskills
無料GitHub で公開

absolute-prune

Dead code and dependency cleanup, repo-wide: unused deps, unreferenced exports, unreachable code, orphaned files — removed only with tool evidence, in reversible waves. Runs on green main. For diff-scoped cleanup use absolute-simplify. Triggers on "absolute prune", "remove dead code", "find unused deps/exports", "what can we delete", "clean up orphaned files".

インストール方法を見る

含まれるファイル(3)

  • SKILL.md4.6 KB
  • README.md722 B
  • references/health-engine.md5.3 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Start your first response with the ✂️ emoji.

Absolute Prune

Cut dead growth from the repo: unused dependencies, unreferenced exports, unreachable code, orphaned files. Evidence-based — every removal is backed by a tool that proves nothing references it — applied in safe waves with tests green after each.

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 pruning.


When to use

  • "Remove dead code", "clean up unused deps", "what can we delete?".
  • Bundle/install bloat from packages nothing imports anymore.
  • Post-refactor orphans: files and exports left behind after a feature was rerouted.

prune vs simplify: simplify polishes your working git diff. prune sweeps the whole committed repo for things that are dead repo-wide. Use simplify mid-change; prune as standing cleanup on green main.


What it scans

Dead dependencies — declared but never imported (and missing deps that are imported but undeclared):

EcosystemTool
JS/TSdepcheck or knip (knip also covers exports/files)
Pythondeptry
Gogo mod tidy (diff), unused module detection

Dead code — unreferenced exports, unreachable branches, orphaned files:

EcosystemTool
JS/TSknip (exports/files), ts-prune, eslint no-unused-vars
Pythonvulture, ruff unused rules
Godeadcode ./..., staticcheck (U1000)

Prefer tools already in the project. Treat results as candidates — verify each isn't reached via dynamic import, reflection, DI, public API, or a config string before removing.


Risk ranking (TRIAGE)

WaveRemovalDefault
1unused devDeps, unreferenced local exports/functionsfix now — lowest risk
2unused runtime deps, orphaned internal filesfix this pass after confirming no dynamic ref
3anything reachable via public API, plugin system, dynamic require, reflection, or configgated / usually defer — high false-positive risk

Static tools miss dynamic references. Anything in wave 3, or anything a tool flags but you can't prove is dead, gets confirmed with the user or deferred — never auto-removed.


Fix & verify

  • Remove in small, reversible waves. One category per wave (e.g. "unused devDeps", then "orphaned files").
  • After each wave: full test + build + typecheck. A green typecheck/build is the proof the removed symbol truly had no references. If anything goes red, the symbol wasn't dead — revert and reclassify.
  • Removing a dep: drop it from the manifest, regenerate the lockfile, rebuild.
  • Don't delete: generated files, vendored code, public-API surface, or anything load-bearing for a config/plugin you can't trace. Report those as "suspected dead, needs human call". Treat preferences.health.protectedPaths from config as never-delete globs — anything matching is out of scope even if a tool flags it.

Gotchas

  1. Trusting the tool blindly. Dynamic imports, DI containers, reflection, and string-keyed lookups defeat static analysis. Confirm before deleting.
  2. Removing public API. A library's unused-internally export may be its whole point. Check the package entry points / exports map.
  3. Deleting generated or vendored files. They look orphaned but are rebuilt/checked-in on purpose.
  4. Big-bang prune. Deleting everything flagged in one commit makes regressions un-bisectable. Wave it.
  5. Scope creep into refactor. prune removes dead things; it does not restructure live code. Restructuring → simplify or work.

Companion commands

  • /absolute simplify — for restructuring/clarity of live code in your diff.
  • /absolute upgrade — pairs well: prune unused deps, then upgrade what remains.
  • /absolute debt — pruning often clears a batch of lint/unused-var warnings too.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Vulnerability and security scan (defensive, your own repo): dependency CVEs plus risky code patterns (secrets, injection, weak authz), severity x reachability triaged and remediated without suppressing. Complements the built-in /security-review. Triggers on "absolute audit", "security audit", "are we vulnerable", "scan for CVEs", "check for secrets/injection", "harden this".

日本語の概要は準備中です。原文の説明を表示しています。

maddhruv/absolute2192026年7月6日 更新

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".

日本語の概要は準備中です。原文の説明を表示しています。

maddhruv/absolute2192026年7月6日 更新

Flaky test fixes: detect nondeterministic tests empirically (repeat/shuffle/parallel runs), diagnose the root cause, fix it — never retry/skip/sleep — and verify across many randomized runs. Triggers on "absolute deflake", "fix flaky tests", "CI is flaky", "this test fails randomly/intermittently".

日本語の概要は準備中です。原文の説明を表示しています。

maddhruv/absolute2192026年7月6日 更新

Diátaxis-driven documentation for AI coding agents: write, improve, or audit tutorials, how-tos, reference, explanation, and developer docs (README, CONTRIBUTING, ADRs). Detects the docs stack; gates on the outline before writing prose; verifies every claim against the code before it ships. Triggers on "absolute docs", "write docs", "write a tutorial", "write a README", "document this", "improve this doc", "audit our docs".

日本語の概要は準備中です。原文の説明を表示しています。

maddhruv/absolute2192026年7月6日 更新

One-time setup for absolute: interview how you want it to behave (output style, autonomy, TDD strictness, spec dir, families) + detect the stack once, then write `.absolute.config.json` (project, committed) and `~/.absolute/config.json` (user defaults + per-project overrides). Every other absolute-* command reads it instead of re-detecting; non-blocking — commands proceed without it and soft-recommend it. Triggers on "absolute init", "set up absolute", "initialize absolute", "configure absolute", "first-time setup", "remember my conventions for this repo".

日本語の概要は準備中です。原文の説明を表示しています。

maddhruv/absolute2192026年7月6日 更新

Use when the user wants to simplify, clean up, refactor, tidy, or refine code — their staged/unstaged git changes or a target file/path. Reduces complexity, flattens nesting, removes redundancy and dead code, scores each change by value (holding low-value churn), then runs tests to prove nothing broke. Invoke on: "simplify", "simplify this", "simplify my code/changes", "clean up", "clean this up", "clean up my changes", "refactor this", "make this cleaner", "tidy this up", "reduce complexity", "flatten this", "remove dead code", "make it more readable", "polish before commit", or "absolute simplify". Acts on your working diff; for repo-wide dead code use absolute-prune; for lint/type debt use absolute-debt.

日本語の概要は準備中です。原文の説明を表示しています。

maddhruv/absolute2192026年7月6日 更新

maddhruv のスキルをすべて見る

このスキルの問題を報告する