ChurchCRMChurchCRM/CRM/.agents/skills/source-command-pr-review/SKILL.md

source-command-pr-review

Skill989 starsChanged 6 days agoMITView on GitHub

Migrated source command `pr-review`

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-prune-branchesSkill
- source-command-push-prSkill
- source-command-repo-healthSkill
- 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, 1 is distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific
could be automatic: a setting could enforce it

Very specific:
Use this skill when the user asks to run the migrated source command pr-review.
line 8
Very specific:
Every draft includes the church-user impact line from pr-review.md Phase 6.
line 27
Distinctive:
Do not approve. Do not merge.
line 28
Very specific:
Do not ask for locale:build.
line 33

≈ “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

source-command-pr-review

Use this skill when the user asks to run the migrated source command pr-review.

Command Template

/pr-review

Review a ChurchCRM pull request using the maintainer gates.

Arguments: a PR number or URL. If omitted, use the PR already in context.

Read in order:

.agents/skills/churchcrm/maintainer-review-gates.md
.agents/skills/churchcrm/pr-review.md
.agents/skills/churchcrm/church-review.md

Rules

Draft in chat first. Do not post until a maintainer says to post.
Every draft includes the church-user impact line from pr-review.md Phase 6.
Do not approve. Do not merge.
Hard blocks → Request changes. Everything else → Comment.
UI changes: require a tablet/mobile manual pass. Ask for screenshots if they exist. Do not block only because shots are missing.
Dates, times, numbers, currency, timezone: follow timezone-handling.md. API/storage is ISO or naive sTimeZone wall-clock. Display settings are not parse formats. Wrong contract is Request changes.
Posted reviews include a checkbox list of what is still open.
Do not ask for locale:build.
Be thankful. Do not nitpick.

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.

Check your setup, free