agile-12-tech-debt-sweep

Name: agile-12-tech-debt-sweep
Availability: InStock
Author: cedricfarinazzo

Audits repositories for tech debt and produces a prioritized cleanup report.

Updated May 16, 2026

Search Tags:#code-cleanup #claude-md #tech-debt #ci-cleanup #repository-audit #skill-md #artifact-mgmt

Ready to run

npx skills add https://github.com/cedricfarinazzo/agile-skills --skill agile-12-tech-debt-sweep

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agile-12-tech-debt-sweep
Source: https://github.com/cedricfarinazzo/agile-skills/tree/main/agile-sprint-close/skills/agile-12-tech-debt-sweep
Command: npx skills add https://github.com/cedricfarinazzo/agile-skills --skill agile-12-tech-debt-sweep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit and streamline sprint closeouts by scanning the repository for cruft, misconfigurations, and unnecessary artifacts, ensuring a clean baseline for agile-13-sprint-closeout.

Core Features & Use Cases

Phase 0 — Inventory: scan repo root and sub-folders for CLAUDE.md, SKILL.md, docker/**, and CI workflows; build a one-line manifest per category.
Phase 1 — Audit (5 categories, all run by default): Cross-repo leakage, CLAUDE.md/SKILL.md cruft, unused CI workflows, heavy Docker rebuild candidates, and misplaced artifacts.
Phase 2 — Report before apply: produce a single markdown report detailing issues, proposed fixes, and preserved behavior; this report is ready for human approval.

Quick Start

Run the tech debt sweep to generate the pre-closeout audit and prepare a prioritized cleanup plan.

Frequently Asked Questions about agile-12-tech-debt-sweep

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

FAQPage Schema

How do I automate tech debt cleanup and identify repository cruft before sprint closeout?▼

Automate tech debt cleanup by scanning repository roots, CI workflows, and docker components to identify cruft, misconfigurations, and cross-repo leakage. This process generates a prioritized markdown report of actionable fixes ready for human approval before sprint closeout.

What is cross-repo leakage and how does a repository audit detect it?▼

Cross-repo leakage occurs when isolated configurations or artifacts improperly reference external repositories. A repository audit detects this by analyzing CLAUDE.md, SKILL.md, and CI workflows to surface misplaced dependencies and ensure proposed changes preserve behavior before applying deletions.

How do I find unused CI workflows and heavy Docker rebuild candidates in my codebase?▼

Find unused CI workflows and heavy Docker rebuild candidates by running an automated audit that inventories CI configurations and docker components. The audit produces a categorized manifest highlighting unnecessary workflows and inefficient rebuild targets requiring cleanup.

Can I automatically delete misplaced artifacts and unused CI workflows during a code cleanup?▼

You cannot automatically delete misplaced artifacts or unused CI workflows during code cleanup. The audit requires explicit human approval before applying any cross-repo moves or deletions, ensuring all proposed changes strictly preserve existing system behavior.

Does the repository audit require any external dependencies to scan CLAUDE.md and SKILL.md files?▼

The repository audit requires no external dependencies to scan CLAUDE.md and SKILL.md files. It operates independently to inventory configuration files, identify cruft, and generate a governance report detailing issues and proposed fixes for end-of-sprint streamlining.