agentleFS
bestdeejay-designbestdeejay-design/agent-skills/skills/github-repo-hygiene/SKILL.md

github-repo-hygiene

Skill6 starsChanged 3 months agoMITView on GitHub

DEPRECATED meta-skill. Routes to the four focused repository skills that replaced it: repo-readme-assets (README + animated SVG header/footer), repo-community-files (LICENSE/CODE_OF_CONDUCT/CONTRIBUTING/SECURITY/SUPPORT/templates), repo-metadata-health (description/topics/GitHub Pages/community health/audit), repo-social-preview (og:image PNG). Load one of the four directly instead. Triggers: 'github hygiene', 'repo polish', 'github repo docs', 'оформить репозиторий', 'репозиторий готов к публикации'.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Keep this router for one release cycle for backward compatibility (global AGENTS.md rules may still reference github-repo-hygiene), then …

    line 34
  2. Very specific:

    Do not use this deprecated router when a focused repo-* skill is applicable.

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

GitHub Repo Hygiene — DEPRECATED (router)

This skill is deprecated. It was split into four focused skills. Do not run workflows from this file — load the matching sub-skill directly.

Routing table

NeedLoad this skill instead
README (EN + localized mirror) + animated SVG header/footerrepo-readme-assets
LICENSE, CODE_OF_CONDUCT, CONTRIBUTING, SECURITY, SUPPORT, issue/PR templates, FUNDINGrepo-community-files
description, topics, GitHub Pages link, community-health audit, 16-point checklistrepo-metadata-health
social preview (og:image) PNG 1280×640repo-social-preview

The old scripts/references were moved into the four new skills:

  • generate_assets.py, validate_svg.py, extract_context.py + svg references → repo-readme-assets
  • validate_repo.py + community-checklist.md + repo-hygiene.yml example → repo-metadata-health
  • generate_social_preview.py + social-preview.md → repo-social-preview

Removal plan

Keep this router for one release cycle for backward compatibility (global AGENTS.md rules may still reference github-repo-hygiene), then delete the folder.

Boundaries

  • Do not use this deprecated router when a focused repo-* skill is applicable.

Router procedure

This skill performs no repository edits. First identify whether the request concerns README assets, community/legal files, GitHub metadata, or the social preview. Load exactly the focused skill from the routing table and carry its verification gate into the final report.

Verification

The router's output must name the selected sub-skill and explain why the other three were not selected. If the request spans areas, compose the focused skills explicitly instead of reviving the deprecated monolithic workflow.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.