← ClaudeAtlas

codebase-maintenancelisted

Run one named, read-only maintenance job for Wollipog and draft evidence-backed findings for approval. Covers architectural simplification, dead code, test value and coverage, stale flags, duplication, docs, flakes, dependencies, and tracker reconciliation. Use when an automation or user asks for a maintenance sweep.
picoduck/wollipog · ★ 3 · AI & Automation · score 69
Install: claude install-skill picoduck/wollipog
# Codebase Maintenance Each job is a narrow, evidence-anchored sweep that runs on a schedule with no human watching it start. The prompt that launches a job is one sentence; this file and the job file are the harness that make the result trustworthy. Read `jobs/<job-id>.md` for the job you were asked to run. That file defines the scope, the tools that produce ground truth, and the gate a finding must pass. This file defines everything the jobs share. For working code that is unnecessarily hard to change, use [architectural-simplification](jobs/architectural-simplification.md). It examines one subsystem's caller burden and design history; literal duplication remains the separate `duplicate-abstraction-unification` job. A schedule or campaign may invoke either job by its exact ID. Changing this skill does not add a job to an existing saved automation. ## Phase 1: Report Only Every job currently runs in report-only mode. A job investigates and drafts; it never changes the repository and never publishes. Hard rules: 1. Do not edit, create, or delete any file in the workspace. Do not commit, branch, stage, stash, push, or open a pull request. A detached analysis worktree under this run's scratch directory is the sole exception to creating workspace files; use it only as described below. 2. Do not run installs, migrations, formatters, code generators, or any command whose purpose is to change the tree. Analysis tooling that writes only to caches, `node_modules/.cach