Menu
Use when starting any conversation in a repo — establishes the repo-hygiene skill set and the moments each sub-skill applies
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when the user asks to "clean up", "apply repo-hygiene to", or "fix the hygiene of" an existing codebase — orchestrates the other hygiene skills in a phased, reviewable order rather than firing a 200-file mega-diff
Use when about to commit, merge, or push — runs verification (tests, typecheck, lint), confirms focus, and checks sibling hygiene (docs, tests, docstrings) BEFORE the commit lands, so "user said commit" doesn't bypass quality
Use when changing a public API surface — renamed export, changed signature/return type, new or removed flag/route/env var, schema migration, deprecation — before committing, so README, docs/, CHANGELOG, and inline references stay coherent with the code
Use when about to add lines to an existing source file, when a single file passes ~400 lines, or when proposing where to put new code — prevents files from sprawling into multi-concern god-modules
Use when starting substantive work in an unfamiliar repo, before diving into task-specific grep or edits — especially when the task touches business logic, public API, build, or infra, or you don't yet know the repo's purpose, stack, conventions, or layout
Use when adding or modifying business logic, branching code, public API, or fixing a bug in a repo using repo-hygiene — tests for the new code paths must exist before the change is committed, not "later" or "if the user asks"
| name | using-repo-hygiene |
| description | Use when starting any conversation in a repo — establishes the repo-hygiene skill set and the moments each sub-skill applies |
This plugin keeps a codebase healthy as you work in it. Each sub-skill triggers on a specific moment — invoke it then via the Skill tool.
Important override: This skill set INVERTS the usual "no comments unless WHY is non-obvious" default. In a repo using this plugin, docstrings on functions and file headers ARE expected. Quality matters (see repo-hygiene:writing-docstrings); silence does not.
| When this happens | Invoke |
|---|---|
| Starting substantive work in a repo you don't already understand | repo-hygiene:orienting-to-repo |
| Writing or modifying a function, class, or source file | repo-hygiene:writing-docstrings |
| About to add lines to a file >400 lines, or your edit pushes one past that | repo-hygiene:keeping-files-small |
| Changing a public API (renamed export, new flag, new route, changed signature) | repo-hygiene:keeping-docs-fresh |
| Adding business logic, branching code, or fixing a bug | repo-hygiene:testing-new-code |
| Drafting any commit message | repo-hygiene:writing-commit-messages |
| User asks to commit, merge, or push | repo-hygiene:gating-commits |
| User asks to "clean up" or apply repo-hygiene to an existing codebase | repo-hygiene:cleaning-existing-codebase |
superpowers:test-driven-development is already in play, testing-new-code is satisfied by that workflow.A user can bypass a hygiene skill for one turn with #hygiene-skip <reason> in their message. Acknowledge the bypass and proceed.