Individual skill
janitor
Improves Git and repository hygiene using project-specific conventions for branches, commits, tags, ignored files, workflows, templates, releases, and public presentation. Use for repository cleanup or commit-message work; gate destructive history or remote operations.
skills/janitor/SKILL.md
Source commit cfa78f744564cec2c5aaf0cbacbada58d79b9e59
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 12
- Repository last updated
- Nov 2, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- agentic-coding Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- code-review Repository topic
- coding-agents Repository topic
- debugging Repository topic
- developer-productivity Repository topic
- developer-tools Repository topic
- llm Repository topic
- operations Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 9,249 bytesSKILL.mdcore · 9,249 bytesreferences/hygiene-checklists.mddoc · 3,803 bytesreferences/maintenance-protocol.mddoc · 3,195 bytesreferences/research.mddoc · 4,250 bytes
Read excerpt
# janitor: git and GitHub hygiene
Everything here is grounded in actual `git`/`gh` output: never assumed.
Destructive operations (history rewrite, force push, branch deletion)
are the user's explicit call, always.
## Prerequisites
A git repository to work in, plus `gh` authenticated only when the task
touches the remote. No repo → say so; hygiene of a non-repo is a
different job (usually `unslop`).
## Authority and action classes
