agentsclimarketplace

Using repo hygiene

Skill gg-mo/repo-hygiene/skills/using-repo-hygiene

Hygiene skills for Claude Code, Codex, Cursor, OpenCode, Gemini, and Copilot — orient, docstring, test, gate commits

Install
npx -y skills add gg-mo/repo-hygiene --skill using-repo-hygiene

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when starting any conversation in a repo — establishes the repo-hygiene skill set and the moments each sub-skill applies

SKILL.md

2.0 KB, as published. Nobody here has run it

<SUBAGENT-STOP> If you were dispatched as a subagent to execute a specific task, skip this skill. </SUBAGENT-STOP>

Using Repo Hygiene

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.

Trigger Table

When this happensInvoke
Starting substantive work in a repo you don't already understandrepo-hygiene:orienting-to-repo
Writing or modifying a function, class, or source filerepo-hygiene:writing-docstrings
About to add lines to a file >400 lines, or your edit pushes one past thatrepo-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 bugrepo-hygiene:testing-new-code
Drafting any commit messagerepo-hygiene:writing-commit-messages
User asks to commit, merge, or pushrepo-hygiene:gating-commits
User asks to "clean up" or apply repo-hygiene to an existing codebaserepo-hygiene:cleaning-existing-codebase

Priority

  1. User instructions win. If the user says "skip the orientation," skip it.
  2. Coordinate with peer skill sets. If superpowers:test-driven-development is already in play, testing-new-code is satisfied by that workflow.
  3. Otherwise apply at the triggers above.

Bypass

A user can bypass a hygiene skill for one turn with #hygiene-skip <reason> in their message. Acknowledge the bypass and proceed.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.