github-repo-standards
Skill0 starsChanged 6 months agoMITView on GitHub
检查和补齐 GitHub 仓库社区标准文件。Use when the user asks to standardize a repository, prepare it for GitHub, add SECURITY.md, CONTRIBUTING.md, CODEOWNERS, issue/PR templates, .gitignore, .gitattributes, README, or CI-related repository hygiene.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- farfarfun-skill/project-managertheir own version, first seen Sep 16, 2026
- farfarfun-skills/farfarfun--project-managertheir own version, first seen Sep 16, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- farfarfun-skill/project-manager★ 0same name
- farfarfun-skills/farfarfun--project-manager★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- claude-config-maintainerSkill
- coderSkill
- engineer-coder-orchestratorSkill
- engineerSkill
- learning-blogSkill
- unity6-projectSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 13
Never include secrets, personal tokens, private keys, or machine-local credentials.
- Distinctive: line 14
Update CLAUDE.md or README.md only when a new important workflow needs to be discoverable.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
GitHub Repo Standards
Workflow
- Scan for existing files before creating anything.
- Report missing or empty community files by priority.
- Fill only the files the user wants, using project facts from the repo.
- Never include secrets, personal tokens, private keys, or machine-local credentials.
- Update
CLAUDE.mdorREADME.mdonly when a new important workflow needs to be discoverable.
Checklist
README.mdCLAUDE.mdorAGENTS.md.gitignore.gitattributes.editorconfigSECURITY.mdCONTRIBUTING.md.github/CODEOWNERS.github/PULL_REQUEST_TEMPLATE.md.github/ISSUE_TEMPLATE/.github/workflows/*.ymlwhen CI is in scope
Templates
- 若
docs/templates/github/存在,先读 README.md 了解模板与源文件关系,优先参照最新源文件生成。 - 若模板目录不存在(未安装 docs),直接根据项目上下文和通用最佳实践生成所需文件,不报错。
- 模板文件头部有
source of truth声明,复制到下游项目时移除该声明行。
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.

