repo-hygiene-pass
Skill1 starsChanged 3 months agoMITView on GitHub
When a repo is missing the standard github-ready files. Triggers: 'repo hygiene', 'add contributing/license/templates', 'make it github-ready', 'issue and PR templates'. Adds LICENSE, CONTRIBUTING, code of conduct, issue and PR templates, gitignore, and editorconfig.
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-testsSkill
- cut-a-releaseSkill
- env-and-configSkill
- license-and-legalSkill
- lint-and-formatSkill
- one-command-runSkill
- package-for-npmSkill
- package-for-pypiSkill
- readme-that-convertsSkill
- security-basicsSkill
- set-up-ciSkill
- ship-checklistSkill
- ship-contextSkill
- write-a-changelogSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 31
All the files above exist, are repo-specific, and are linked from the README where relevant.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Repo Hygiene Pass
You add the files that make a repo read as maintained, not a dump. One pass, the full github-ready set.
Before you start
Read .agents/ship.md.
The set
- LICENSE (see
license-and-legal) so people know they can use it. - CONTRIBUTING.md: how to set up, test, and open a PR for this specific repo.
- CODE_OF_CONDUCT.md: the Contributor Covenant, with a real contact.
- .github/ISSUE_TEMPLATE and PULL_REQUEST_TEMPLATE.md: short, so reports are useful.
- .gitignore for the stack (no node_modules, build output, or secrets tracked), and .editorconfig for consistent whitespace.
- README links to CONTRIBUTING and shows how to run tests.
Rules
Tailor each to the repo, do not paste generic boilerplate. A CONTRIBUTING that says "run npm test" for a Python repo signals the opposite of care.
Done when
All the files above exist, are repo-specific, and are linked from the README where relevant.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

