# Quality Sweep > Audit and implement behavior-preserving cleanup across types, dead code, dependencies, errors, and comments - Skill: `georgeqle/quality-sweep` (Agent Skill, multi-file: 4 files) - Install (CLI): `npx skillmds@latest add georgeqle/quality-sweep` - Raw SKILL.md: https://api.skillmd.com/api/skills/georgeqle/quality-sweep/raw - Safety review: CAUTION (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Security - Author: GeorgeQLe (https://skillmd.com/u/georgeqle) - Updated: 2026-08-19 - Page: https://skillmd.com/skills/georgeqle/quality-sweep --- # Quality Sweep Invoke as `$quality-sweep`. Use this skill when a project needs a behavior-preserving code quality cleanup campaign across duplication, type hygiene, dead code, dependency boundaries, defensive error handling, legacy paths, and comments. This skill orchestrates cleanup work; use narrower skills like `extract-shared-types`, `dead-code`, `slim-audit`, `hygiene`, `spec-drift`, and `regression-check` when the user asks for only one of those concerns. ## Process 1. **Select mode and scope.** - Parse `$ARGUMENTS` for mode: `audit`, `fix`, or `full`. - Default to `audit` when no mode is provided. - Treat remaining arguments as the target scope: package, app, directory, or domain. - If no scope is provided, inspect the repository and choose the smallest coherent scope before broadening. 2. **Establish baseline and context.** - Read project instructions, manifests, package configs, path aliases, lint/typecheck/test/build scripts, and relevant docs. - Read specs, roadmap/todo/history, changelogs, ADRs, or design notes when present. - In `fix` or `full`, run or record the narrowest relevant baseline checks available before edits. - Respect documented trade-offs and intentional architecture. Do not report documented decisions as cleanup targets. 3. **Run audit lanes.** - **Duplication:** find duplicate or near-duplicate code where consolidation reduces coupling, maintenance cost, or complexity. - **Shared types:** find type definitions that should move to a shared boundary; follow `extract-shared-types` rules for any implementation. - **Unused code:** use code search and available tools such as `knip` to find unused exports, orphaned files, stale dependencies, and unreachable branches. - **Circular dependencies:** use code search and available tools such as `madge` to identify dependency cycles and import-boundary issues. - **Weak types:** find unsafe `any` and unjustified weak typing. Preserve `unknown` at trust boundaries unless a stronger validated type exists. - **Error handling:** audit `try`/`catch` and defensive patterns. Preserve boundary handling, parsing, cleanup, rollback, external-service handling, and error translation. - **Legacy paths:** find deprecated, migration, compatibility, fallback, and alternate code paths that may now be obsolete. - **Comments and stubs:** remove or rewrite AI slop, stale comments, in-motion notes, stubs, larp, and comments that describe previous work instead of current behavior. 4. **Triage every finding.** - `Safe to Fix`: behavior-preserving, statically supported, verified by code search, not public-API-sensitive, and independently revertible. - `Needs Investigation`: plausible but ambiguous, migration-sensitive, weakly covered, or dependent on product intent. - `Do Not Change`: documented decision, necessary fallback, valid boundary handling, or readability-preserving duplication. - Re-read the relevant source before finalizing a finding. Drop findings that cannot be reconfirmed. 5. **Use subagents only for audit-first lanes.** - If the user explicitly requests subagents, or the mode is `full` and the active environment permits subagents, assign lanes as research tasks first. - Subagents should report findings and recommendations before edits. - The main agent owns final triage, integration, edits, and verification. - Direct subagent edits are allowed only when the main agent assigns disjoint file or path ownership. 6. **Implement only approved safe cleanup in `fix` or `full`.** - Do not modify files in `audit` mode. - Batch changes by lane or subsystem. - Avoid broad abstractions unless they reduce real complexity or coupling. - Do not remove public import paths, compatibility shims, migrations, or fallbacks unless evidence shows they are obsolete. - Do not replace `unknown` with weaker or speculative types. - Do not remove error handling that defines a clear boundary, adds actionable context, performs cleanup, or preserves system integrity. - Re-run the narrowest relevant validation after each meaningful batch. 7. **Verify and report.** - Run relevant typecheck, lint, tests, build, dead-code checks, and circular-dependency checks when available. - Distinguish new failures from pre-existing baseline failures. - If validation fails in `fix` or `full`, fix the regression or stop and report the blocker. ## Output - **Summary:** mode, scope, tools/checks used, and overall cleanup potential. - **Safe to Fix:** concrete items with file references, evidence, proposed change, and validation path. - **Implemented:** for `fix` or `full` only; grouped by batch with files changed. - **Needs Investigation:** skipped items and why they need more evidence or product input. - **Do Not Change:** suspicious-looking patterns intentionally preserved. - **Verification:** commands run, pass/fail status, and pre-existing failures if any. ## Alignment Page Follow the shared alignment-page convention via the packaged convention resolver; output path is `alignment/quality-sweep-{topic}.html`. ## Constraints - Audit-only by default. Never edit files unless mode is `fix` or `full`. - Behavior preservation is the default. Treat public APIs, package exports, migrations, database/data compatibility, and external contracts as high risk. - Prefer repository-native tooling and existing dependencies. Do not add cleanup tools unless the user explicitly approves. - Be conservative with deletion. Static analysis findings must be verified with code search and source inspection. - Do not use DRY as a blanket rule. Consolidate only when it reduces real maintenance burden without hiding distinct reasons to change. - Keep comments only when they explain intent, constraints, invariants, or non-obvious behavior for a future maintainer. ## Default Shipping Contract Follow the shared shipping contract convention in CLAUDE.md.