source-command-repo-health
Skill989 starsChanged 8 days agoMITView on GitHub
Migrated source command `repo-health`
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- churchcrmSkill
- source-command-church-reviewSkill
- source-command-pr-reviewSkill
- source-command-prune-branchesSkill
- source-command-push-prSkill
- source-command-security-advisorySkill
- source-command-security-report-triageSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this skill when the user asks to run the migrated source command repo-health.
- Very specific: line 14
Run the on-demand GitHub health snapshot defined in .agents/skills/churchcrm/repo-health.md: approved PRs waiting to merge, the …
- Distinctive: line 16
Read that skill file now and follow it exactly — its Setup, Check 1–4, and Report sections are the actual instructions.
- Distinctive: line 18
If the request names a specific check ("any approved PRs waiting?", "clean up stale branches"), run only that check.
≈ “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
source-command-repo-health
Use this skill when the user asks to run the migrated source command repo-health.
Command Template
Repo Health Check
Run the on-demand GitHub health snapshot defined in .agents/skills/churchcrm/repo-health.md: approved PRs waiting to merge, the good-first-issue pipeline, community-profile hygiene, and stale-branch cleanup.
Read that skill file now and follow it exactly — its Setup, Check 1–4, and Report sections are the actual instructions. This command is a pointer, not a copy, so the skill file is the one place to update when the checks change.
If the request names a specific check ("any approved PRs waiting?", "clean up stale branches"), run only that check. Otherwise run all four, worst-first, per the skill's Report section.
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.

