darkmatter/skills

codebase-cleanup

Multi-pass refactor / code-quality cleanup designed to be dispatched as 8 specialist subagents (one per cleanup concern), each running a research → critical-assessment → high-confidence-implementation cycle.

Vedi sorgente
Documento Skill originale

Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.

Codebase cleanup — 8-pass refactor

Eight independent specialist passes over a codebase, each scoped to one quality concern. Designed to be run as 8 separate subagent sessions (or sequentially in one) so each pass gets a clean context window and can't be tempted to bleed into another's territory.

Every pass follows the same three-phase protocol — see reference/protocol.md. The recommended pass ordering and why is in reference/pass-ordering.md.

Apply codebase-design throughout: keep each capability together, expose complete operations, and extract only when the split hides complexity or enables useful reuse. Preserve configured line limits with documented, targeted exceptions. File count and net deleted lines are not goals.

When to use

  • "Clean up the codebase" / "do a tech-debt pass"
  • "Refactor for quality before we ship"
  • "Find and remove dead code / AI slop / weak types"
  • Onboarding a codebase and wanting to know what's actually load-bearing
  • Pre-1.0 / pre-release quality sweep
  • Periodic (quarterly) hygiene runs

When NOT to use

  • Narrow targeted asks ("remove this one function", "fix this one type")
  • Net-new feature work
  • Tight deadline / minimum-viable-fix scenarios — this is a deliberate, careful sweep
  • Codebases under active heavy refactor by humans (the passes will fight in-flight work)

The 8 passes

Run in this order (rationale in reference/pass-ordering.md). Each links to the full subagent prompt:

  1. AI slop & stale commentsreference/passes/01-ai-slop.md

Remove generated noise, in-motion-work comments, larp, unhelpful boilerplate.

  1. Legacy / deprecated / fallback codereference/passes/02-legacy-removal.md

Remove dead branches, deprecated APIs, fallback paths that no longer fall back to anything live.

  1. Unused codereference/passes/03-unused-code.md

knip-class analysis: exports/files/deps that nothing imports.

  1. Circular dependenciesreference/passes/04-circular-deps.md

madge-class analysis: untangle import cycles.

  1. Weak typesreference/passes/05-weak-types.md

Replace any / unknown / Object / dynamic / interface{} with real types backed by research.

  1. Type consolidationreference/passes/06-type-consolidation.md

Find duplicated / near-duplicated type definitions and unify.

  1. Defensive programmingreference/passes/07-defensive-programming.md

Remove try/catch and null-guards that don't handle a real input boundary.

  1. DRY / dedupreference/passes/08-dry.md

Consolidate duplicated logic only where it reduces complexity (not the other way).

Tools

Each pass spec lists the tooling it expects (knip, ts-unused-exports, madge, jscpd, language-specific linters, etc.). The skill ships no scripts — orchestration happens in the calling agent runtime, which already has bash/edit/grep/etc.

Reference

  • reference/protocol.md — the 3-phase research/assess/implement protocol every pass follows
  • reference/pass-ordering.md — why this order, and which passes can run in parallel
  • reference/passes/*.md — one self-contained subagent prompt per pass
dallo stesso repository

Altri Skills

Tutti gli Skills
darkmatter
Community

darkmatter-repo-setup

- Use when setting up a new repo, onboarding an existing repo to darkmatter standards, running a compliance check, or when the user says "set up this repo", "bring repo up to standards", "apply template", or "audit repo". Checks and installs the org TypeScript toolchain (Bun, tsgo, oxlint/oxfmt, Vitest), Nix flake-parts devshell, ops/ surface, CI pipeline, and AGENTS.md conventions.

installazioni
1
GitHub Stars
0
Aggiornato
18 set
darkmatter
Community

darkmatter-ts-toolchain

The darkmatter TypeScript toolchain contract: Bun, tsgo, Vitest, oxlint/biome, changesets, Effect I/O, Alchemy deploys, and required checks. Use when writing, fixing, building, or shipping TypeScript in a darkmatter repo. Use codebase-design for module boundaries and effect-typescript for deep Effect patterns.

installazioni
1
GitHub Stars
0
Aggiornato
18 set
darkmatter
Community

run-ui-registry-variations

Manual-invocation skill — run only when the user explicitly asks for "run-ui-registry-variations" or invokes it as a slash command. Do not auto-trigger on adjacent topics. Force UI work through shadcnblocks, Aceternity, or https://shadcn.darkmatter.io; validate private registry access before use; build exactly three user-reviewable variations.

installazioni
1
GitHub Stars
0
Aggiornato
10 set
darkmatter
Community

test-driven-development

Use when the user asks for TDD, test-first, red-green-refactor, or an end-to-end happy-path test of a public contract. Do not use for ordinary implementation, refactors, helpers, or comment-only changes.

installazioni
1
GitHub Stars
0
Aggiornato
10 set