code-cleaner

Audits codebases with aislop and fallow to produce prioritized cleanup plans with complexity estimates.

Updated Nov 25, 2024
One-click install
npx skills add https://github.com/cbrostrom/dotfiles --skill code-cleaner-cbrostrom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-cleaner
Source: https://github.com/cbrostrom/dotfiles/tree/main/stow/agents/.agents/skills/code-cleaner
Command: npx skills add https://github.com/cbrostrom/dotfiles --skill code-cleaner-cbrostrom

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires aislop, fallow.

What problem does it solve? Codebases accumulate AI-generated slop, dead code, duplication, and complexity over time, and teams lack a structured way to measure these issues and decide which fixes are worth doing. This Skill runs deterministic audit tools, categorizes findings by severity, and estimates the effort and model tier needed for each fix before any code is touched. ## Core Features & Use Cases - Deterministic Scanning: Runs aislop on all projects and fallow on JS/TS projects to detect security issues, AI slop, complexity, dead code, and duplication. - Prioritized Findings Report: Groups issues into High/Medium/Low tiers with file and line references, fix approaches, and complexity estimates. - Model Recommendation: Maps each fix tier to an appropriate LLM (from lightweight models for trivial deletions to frontier models for architectural refactors) with escalation triggers. - Permission-Gated Execution: Never modifies code without an approved plan, fixes one category at a time, and re-scans after each pass to report score deltas. - Use Case: After a sprint of AI-assisted coding, ask for a code health audit to get a scored report of security findings, duplicated logic, and unused exports, plus a recommended model and budget tier for the cleanup work. ## Quick Start Ask the agent to audit this repository's code health and present a prioritized cleanup plan with complexity estimates before making any changes.

Frequently Asked Questions about code-cleaner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit code quality with aislop and fallow?▼

Run aislop scan for all projects, and fallow audit --format json --quiet for JS/TS projects with a package.json. The Skill categorizes findings into security, AI slop, complexity, dead code, and duplication, then presents a prioritized plan.

What does the code-cleaner skill detect in a codebase?▼

It detects security vulnerabilities, AI-generated slop patterns, excessive complexity, dead code, and duplicated logic. Findings are grouped by severity: security is high priority, slop and complexity are medium, and dead code and duplication are low.

Does fallow work on non-JavaScript projects?▼

No, fallow audit only runs on JS/TS projects that contain a package.json file. For other projects, only aislop scan is executed, which covers security, AI slop, and complexity rules.

Why does fallow exit with code 1 during an audit?▼

Exit code 1 from fallow means issues were found, which is normal and expected during an audit. Exit code 2 indicates a real error. The Skill always appends || true so findings do not interrupt the workflow.

Can the skill fix code automatically after scanning?▼

No, it never modifies code without explicit permission. It first presents a plan with findings, complexity estimates, and a model recommendation, then fixes one category at a time only after approval, re-scanning after each pass.

When should I not use automated code audit tools?▼

Avoid relying on them for architectural decisions, which the Skill explicitly escalates to the user. They also should not be used to suppress rules for better scores, since the Skill prohibits disabling rules instead of fixing underlying issues.