repo-tidy

Automate plan-driven repository cleanup with staged changes and archive storage.

1|Updated Jul 14, 2026
One-click install
npx skills add https://github.com/TzJ2006/gadget --skill repo-tidy-tzj2006
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-tidy
Source: https://github.com/TzJ2006/gadget/tree/main/skills/repo-tidy
Command: npx skills add https://github.com/TzJ2006/gadget --skill repo-tidy-tzj2006

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

repo-tidy helps tame messy repos by safely cleaning junk, archiving stray files, and giving a clear git-state plan, all with a conservative, reversible workflow.

Core Features & Use Cases

  • Pre-flight backup via git stash to protect active work
  • Type-based cleaning rules for code/docs/data/general repos
  • Explicit plan-and-execute workflow with archive storage

Quick Start

Ask repo-tidy to run in interactive mode to scan your repo, propose a plan, and apply safe cleanup.

Frequently Asked Questions about repo-tidy

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

FAQPage Schema
How do I safely clean up a messy git repository without losing tracked files?

Safe git repository cleanup requires a plan-driven workflow that stages changes, scans for junk, and archives stray files. Using a pre-flight git stash backup protects active work before removing misplaced files and improving git hygiene.

What is the best way to organize and archive stray files in a code repo?

The best way to archive stray files in a code repo is using a five-phase process that scans for misplaced files, proposes an explicit cleanup plan, and moves junk to archive storage. This plan-then-execute workflow ensures files are safely stored rather than auto-deleted.

How do I tidy up a repository containing mixed code, docs, and data files?

To tidy a mixed repository, apply type-based cleaning rules that identify the repo as code, docs, data, or general. The cleanup workflow scans for junk and misplaced files specific to that repository type before proposing a safe, archival-based organization plan.

Does repo-tidy support data and documentation repositories or only code projects?

Yes, repo-tidy supports data and documentation repositories alongside code projects. It identifies the repository type during scanning and applies type-specific cleaning rules to handle the unique hygiene requirements of mixed, data, or doc-centric repos.

Can I review a repository cleanup plan before any files are moved or deleted?

Yes, you can review the cleanup plan before execution. The workflow explicitly separates scanning and planning from execution, proposing a detailed plan of junk removal and archival actions that you must approve before any changes are applied.

When should I avoid automatic repository cleanup tools?

You should avoid unguarded automatic cleanup when working with tracked files or critical archives. A safe tidying process uses guardrails to prevent touching tracked files, avoids auto-deleting archives, and requires a pre-flight git stash to ensure reversibility.