agentleFS
Sign inStart free
ChurchCRMChurchCRM/CRM/.agents/skills/source-command-push-pr/SKILL.md

source-command-push-pr

Skill989 starsChanged 6 days agoMITView on GitHub

Push the current branch and open its pull request

  • Commits and pushes

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 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.

  • 2

    Very specific

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

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

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

    line 8
  2. Distinctive:

    Stop on master. Stop and list the changes if the tree is dirty.

    line 16
  3. Very specific:

    Run npm run lint. Never --no-verify.

    line 17

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

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

Command Template

/push-pr

Push the current branch and open its pull request, following .agents/skills/churchcrm/git-workflow.md. Typing this command is the approval to push.

  1. Stop on master. Stop and list the changes if the tree is dirty.
  2. Run npm run lint. Never --no-verify. On failure, report it and stop.
  3. git push -u origin <branch>. If the branch already has an open PR, push only.
  4. gh pr create --base master. Follow .agents/skills/pr-description-guidelines.md: imperative title under 72 chars, body that matches the current diff, Fixes #N for user-visible changes (otherwise say why there is no issue), the UI pass statement for UI changes, and the attribution line from the session.
  5. Labels are exact names from gh label list --repo ChurchCRM/CRM. No milestone.
  6. Report the PR URL.

Arguments are extra instructions for the PR body.

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