repo-cleanup
Systematic cleanup of repository clutter including build artifacts, duplicates, temp files, and consolidation of scattered directories. Use for repository maintenance, artifact removal, directory consolidation, and gitignore updates.
Best use case
repo-cleanup is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Systematic cleanup of repository clutter including build artifacts, duplicates, temp files, and consolidation of scattered directories. Use for repository maintenance, artifact removal, directory consolidation, and gitignore updates.
Teams using repo-cleanup should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/repo-cleanup/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How repo-cleanup Compares
| Feature / Agent | repo-cleanup | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Systematic cleanup of repository clutter including build artifacts, duplicates, temp files, and consolidation of scattered directories. Use for repository maintenance, artifact removal, directory consolidation, and gitignore updates.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Repo Cleanup ## When to Use - Repository has accumulated build artifacts and temp files - Multiple agent/coordination directories scattered in root - Log files and coverage reports cluttering the workspace - Need to consolidate prototype code and test outputs - Preparing for a clean commit or release - After major refactoring work ## Related Skills - [module-based-refactor](../module-based-refactor/SKILL.md) - For restructuring after cleanup - `coordination/session-start-routine/SKILL.md` - Session initialization ## References - Git clean documentation: https://git-scm.com/docs/git-clean - Git rm documentation: https://git-scm.com/docs/git-rm - Gitignore patterns: https://git-scm.com/docs/gitignore --- ## Version History - **2.2.0** (2026-01-20): Added Benchmark Cleanup and Plan File Archival patterns - Added Benchmark Artifacts section for handling benchmark directories - Added Plan Files section for archiving completed specifications - Added benchmark patterns to .gitignore recommendations - Updated checklist with benchmark and plan archival items - **2.1.0** (2026-01-20): Added Final Cleanup Checklist and README Update Checklist - Added Final Cleanup Checklist with verified DELETE/CONSOLIDATE/KEEP tables - Confirmed .drcode/ as safe to delete (legacy AI config) - Added .slash-commands/ consolidation to .Codex/docs/commands/ - Added .git-commands/ consolidation to scripts/git/ - Added .benchmarks/ as safe to delete if empty - Added README Update Checklist for structure documentation - Added example README structure section template - Added references to remove checklist - **2.0.0** (2026-01-20): Major update with hidden folder cleanup learnings - Added Hidden Folder Cleanup section with legacy AI folder patterns - Added Consolidation Merge Strategies for conflict resolution - Added File Count Verification for tracking consolidation progress - Updated Cleanup Checklist with hidden folder review items - Documented patterns for .agent-os, .ai, .agent-runtime, .common, .specify, .drcode, .slash-commands - **1.0.0** (2025-01-20): Initial release based on digitalmodel repository cleanup session ## Sub-Skills - [Best Practices](best-practices/SKILL.md) ## Sub-Skills - [Version Metadata](version-metadata/SKILL.md) - [1. Build Artifacts (+5)](1-build-artifacts/SKILL.md) - [Agent Directories (+4)](agent-directories/SKILL.md) - [Common Hidden Folders (+2)](common-hidden-folders/SKILL.md) - [Conflict Resolution Patterns (+2)](conflict-resolution-patterns/SKILL.md) - [Progress Tracking Commands (+1)](progress-tracking-commands/SKILL.md) - [List Untracked Files (+3)](list-untracked-files/SKILL.md) - [For Tracked Files (Use git rm) (+2)](for-tracked-files-use-git-rm/SKILL.md) - [Gitignore Updates](gitignore-updates/SKILL.md) - [Pre-Cleanup (+7)](pre-cleanup/SKILL.md) - [Folders to DELETE (Confirmed Safe) (+3)](folders-to-delete-confirmed-safe/SKILL.md) - [Structure Section Updates (+1)](structure-section-updates/SKILL.md) - [References to Remove](references-to-remove/SKILL.md)
Related Skills
interactive-report-generator
Generate interactive HTML reports with Plotly visualizations from data analysis results. Supports dashboards, charts, and professional styling.
data-validation-reporter
Generate interactive validation reports with quality scoring, missing data analysis, and type checking. Combines Pandas validation, Plotly visualization, and YAML configuration for comprehensive data quality reporting.
repo-ecosystem-hygiene
Interpret the daily read-only repo ecosystem hygiene audit and route remediation through approved workflows.
mnt-analysis-cleanup
Survey, classify, and clean up `/mnt/local-analysis/` (or any sibling-to-workspace-hub directory holding orphan worktrees, codex-burn artifacts, agent log accumulations, and outer-clone duplicates) without losing useful code/work. Surfaces a tiered approval menu rather than baking decisions; defers all destructive ops until user confirms.
orcaflex-reporting-fixture-proof-pattern
Build and extend fixture-backed OrcaFlex reporting proof paths in digitalmodel using stable metadata baselines, normalized HTML snapshots, and reusable reporting test helpers.
pre-completion-cleanup-audit
Audit and dispose of session residue (orphan files, scratch dirs, sibling-repo state, locks, trash-stages) BEFORE claiming a task complete. Required gate before any agent says "all done", "task complete", or hands work back to user/orchestrator.
repo-sync
Smart repository synchronization across workspace-hub ecosystem — diagnoses and fixes pull failures (detached HEAD, diverged branches, uncommitted changes)
repo-structure
Canonical source layout, test mirroring, root cleanliness, gitignore, docs classification, and committed artifact rules for all workspace-hub tier-1 repos. Consult before creating directories or files in any submodule.
repo-portfolio-steering
Generate a one-page portfolio steering report for workspace-hub. Use when the user invokes /repo-portfolio-steering, asks about harness vs engineering balance, wants a portfolio health check, or asks which repos to fund next. Reports on portfolio steering, GTM readiness, and provider activity balance.
repo-mission-portfolio-audit
Audit the workspace-hub repo portfolio to extract each repo's mission, identify documentation gaps, and prioritize a plan/approval sequence with explicit LLM-wiki weighting for future issue triage.
mixed-ops-vs-repo-fix-plan-boundary
Plan mixed operational-vs-repo remediation issues by proving live-state classification first, then only proposing code changes for confirmed repo-owned failure paths.
repo-separation-for-sensitive-data
Architecture pattern for splitting confidential data and reusable algorithms across repos