Clean the repository
SkillProductivityLets your agent clean up its local repository checkout after a pull request merges, like deleting merged branches and resyncing master.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Clean the repository skill
About this capability
Clean the local hacs_waste_collection_schedule repository after a pull request merges. Use when a maintainer asks to clean merged branches, resync master, prune remotes, or prepare the checkout for the next ticket.
What this skill tells your AI
The instructions your AI receives, as published by mampfes/hacs_waste_collection_schedule in .agents/skills/cleanup/SKILL.md and read by ahel’s review.
- Spawn the
repo-cleanupcustom agent with this task:Run the full post-merge cleanup workflow. Preserve all personal and tool-local files, confirm every destructive action, and report the final state. - Keep all cleanup work in the main checkout. Do not create an agent worktree.
- Preserve
CLAUDE.local.md,.claude/settings.local.json,.claude/worktrees/,.codex/,.agents/skills/, and any*.local.*path unless the user explicitly targets it. - Require the agent to confirm the merged PR, uncommitted-change handling, branch deletions, force deletions, remote deletions, and
origin/masteroverwrite separately as its instructions require. - Present the agent's cleanup report to the user. Surface any skipped or blocked step; do not imply the repository is clean unless the final checks prove it.
Signals
- GitHub stars
- 2k
- Forks
- 1k
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
cleanup-mampfes- Source
- github.com/mampfes/hacs_waste_collection_schedule