repo-hygiene

Audits repository structure, naming, gitignore coverage, and CI configuration for OSS cleanliness.

218|11|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/baseballyama/rsvelte --skill repo-hygiene-baseballyama
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-hygiene
Source: https://github.com/baseballyama/rsvelte/tree/main/.claude/skills/repo-hygiene
Command: npx skills add https://github.com/baseballyama/rsvelte --skill repo-hygiene-baseballyama

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Repositories accumulate dead files, inconsistent naming, stale documentation references, and missing .gitignore entries over time, making them harder for open-source contributors to navigate and maintain. ## Core Features & Use Cases - Dead file and artifact detection: Finds backup files, empty directories, tracked generated files, and large binaries committed to git history. - Convention enforcement: Verifies kebab-case scripts, snake_case Rust files, .gitignore coverage, and documentation link validity. - CI and dependency audit: Checks that workflow-referenced scripts exist, actions are pinned, and Cargo/npm dependencies are actually used. - Use Case: Before opening a project to external contributors, run the audit to get a categorized report of [ok], [fix], and [ask] items, then auto-apply safe fixes and commit the cleanup. ## Quick Start Ask the assistant to run the repo-hygiene audit on this repository and report dead files, naming inconsistencies, and missing .gitignore entries.

Frequently Asked Questions about repo-hygiene

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

FAQPage Schema
How do I find and remove dead files in a git repository?▼

Run find commands matching backup patterns like *.bak, *.orig, .DS_Store, and empty directories, excluding node_modules and target. Dead files are removed with git rm, while tracked generated files are added to .gitignore and untracked with git rm --cached.

How to check for unused scripts in a repository?▼

Search for references to each script filename across package.json, README, CI workflows, and source directories. Scripts with zero references and no documentation are flagged for user decision rather than deleted automatically.

Does this audit modify source code logic?▼

No, the audit never modifies source code logic. It only addresses repository structure, naming, configuration, and documentation, and all deletions require explicit user confirmation before execution.

What files are protected from deletion during cleanup?▼

Protected files include CI ratchet files like known-failures JSON, checked-in gate inputs, git submodules, generated fixture directories, PGO profiling data, and upstream issue indexes. These are shrink-only CI inputs or pinned corpus sources.

How do I detect large binaries committed to git history?▼

Use git rev-list --objects --all piped to git cat-file --batch-check to list blobs by size, then sort descending. Build artifacts like .wasm, .node, and platform binaries must not be tracked in the repository.