# Git Clean

> This skill should be used when the user asks to "clean the repository", "remove stale branches", "clear old stashes", "manage git hygiene", or "scan for redundant worktrees". Uses the @kurokeita/git-clean-up tool to audit and safely remove unused Git resources.

- Skill: `kurokeita/git-clean` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add kurokeita/git-clean`
- Raw SKILL.md: https://api.skillmd.com/api/skills/kurokeita/git-clean/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: kurokeita (https://skillmd.com/u/kurokeita)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/kurokeita/git-clean

---


# Git Clean Skill

Maintain repository hygiene by scanning for and removing stale branches, forgotten stashes, and redundant worktrees using the `@kurokeita/git-clean-up` tool.

## When to Use This Skill

- Auditing the repository for stale or merged branches.
- Cleaning up old stashes or redundant Git worktrees.
- Improving local performance by removing unneeded Git objects.
- Automating repository hygiene tasks.

## Workflow

Follow this procedure to safely clean the repository:

### 1. Detect package runner

Determine whether to use `pnpx` or `npx` by checking if `pnpm` is installed. Always prioritize `pnpx`.

```bash
# Check for pnpm
pnpm --version
```

- If `pnpm` is available: Use `pnpx @kurokeita/git-clean-up`
- If `pnpm` is NOT available: Use `npx @kurokeita/git-clean-up`

### 2. Audit findings

Run an initial scan using the `--json` flag to identify hygiene issues without making any changes. This enables precise analysis of the findings.

```bash
<runner> @kurokeita/git-clean-up scan --json
```

### 3. Present report

Summarize the findings for the user, categorized by:

- **Branches**: Merged, squash-merged, or branches without upstreams.
- **Stashes**: Old stashes or stale WIPs.
- **Worktrees**: Missing paths or detached HEADs.

### 4. Solicit confirmation

Present the findings to the user and ask which items or categories they would like to clean. Do NOT proceed to deletion without explicit user approval.

### 5. Preview cleanup (Optional but Recommended)

If the user wants to see exactly what will be deleted for a specific selection, run the clean command without the `--apply` flag.

```bash
# Preview all deletions
<runner> @kurokeita/git-clean-up clean --all

# Preview specific categories
<runner> @kurokeita/git-clean-up clean --include branches,stashes
```

### 6. Execute cleanup

After receiving confirmation, run the clean command with the `--apply` flag.

```bash
# Clean everything confirmed
<runner> @kurokeita/git-clean-up clean --apply --all

# Clean specific categories
<runner> @kurokeita/git-clean-up clean --apply --include branches
```

## Safety Considerations

- **Protected Branches**: The tool automatically protects `main`, `master`, `develop`, and `dev`. Do not attempt to override these protections unless explicitly instructed.
- **Active Branches**: Branches checked out in other worktrees are skipped by default.
- **Verification**: Always verify the list of findings with the user before applying deletions.

## Additional Resources

### Reference Files

- **`references/tool-options.md`**: Detailed CLI options and configuration settings for `git-clean-up`.

### Example Configurations

- **`examples/config.json`**: Sample `.git-clean-up.json` for repository-specific hygiene policies.