repo-janitor

Audit repositories for orphan files, broken links, and temporary files.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/lucasmiachon-blip/aula.cirrose --skill repo-janitor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-janitor
Source: https://github.com/lucasmiachon-blip/aula.cirrose/tree/main/.claude/skills/repo-janitor
Command: npx skills add https://github.com/lucasmiachon-blip/aula.cirrose --skill repo-janitor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits repositories to identify and report debris such as orphan files, broken MD links, dead HTML, and temporary files to keep the codebase clean and consistent. It runs in a read-only default mode and can operate with an explicit --fix flag when cleanup is approved.

Core Features & Use Cases

  • Detect orphan files not referenced by manifests or correct imports.
  • Detect broken Markdown links and dead HTML references.
  • Find temporary files (tmp, bak, .DS_Store, Thumbs.db, etc.) and empty directories.
  • Worktree-aware scanning to correctly reference the repo root.
  • Generates structured reports suitable for QA, ZIP exports, or pre-release cleanups.

Quick Start

Run the repo-janitor in your repository to audit for debris and apply fixes with --fix after review.

Frequently Asked Questions about repo-janitor

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

FAQPage Schema
How do I find orphan files and broken links in my repository?

You can identify orphan files and broken links by running a read-only repository audit. The scan detects unreferenced assets, dead HTML, and broken Markdown links, generating a structured report of all debris without modifying your files.

What is the safest way to clean up temp files and empty directories before a release?

The safest cleanup method is a read-only audit that identifies temp files and empty directories, followed by an explicit --fix workflow. This two-step process ensures you review all debris before applying changes to your repository.

Can I audit documentation repositories with _manifest.js, docs, and slides folders?

Yes, the audit works with documentation repositories containing _manifest.js, docs, and slides folders. It is worktree-aware and specifically targets debris created by ongoing refactors in these structures.

How do I actually remove dead HTML and temporary files after the audit?

To remove dead HTML and temp files, you apply the explicit --fix workflow after reviewing the audit report. The tool operates in read-only mode by default, requiring this flag to execute approved deletions safely.

Does repository cleanup work with large codebases that have ongoing refactors?

Yes, repository cleanup supports codebases of any size with ongoing refactors. The worktree-aware scanning correctly references the repo root to accurately identify orphan files and broken links across complex structures.