agentleFS
Sign inStart free
RemiMyrsetRemiMyrset/roots/.agents/skills/pr/SKILL.md

pr

Skill0 starsChanged 42 days agoMITView on GitHub

Push the current feature branch and open a pull request. Verify first, check the branch name against the protected list, build the PR body from the repository template with the checklist ticked only where true, link the issue. Use when the user says "open a PR", "create a pull request", "push and PR", or "ship this branch". Never merges and never touches a protected branch.

  • 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:

    Verify. pnpm verify must pass.

    line 25
  2. Very specific:

    Create. gh pr create --base <default branch> --title "<conventional subject>" --body-file <the filled body>.

    line 37
  3. Distinctive:

    If the request names the issue to close or the PR title, use them.

    line 43

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

Open a pull request

In Claude Code the push flow runs unattended: git push and the read-only gh commands are allow-listed (Codex and Gemini prompt for each), and the deny-push-protected guard keeps every push off a protected branch. What counts as protected, and what else the guard denies, is under "Push protection" in docs/template/guards.md. Merging is a human decision; gh pr merge is not allow-listed, so it prompts unless the session auto-approves, and this skill never runs it.

  1. Branch check. git branch --show-current must not match a protected pattern. If it does, stop and suggest a branch: feat/, fix/, docs/, chore/, or refactor/ plus a short kebab slug, then git switch -c that branch (Claude Code asks first; the allowlist leaves git switch out) and continue.
  2. Clean tree. git status --porcelain must be empty; commit pending work first with a Conventional Commit (type(scope): subject, subject at most 50 chars). Never --no-verify: fix what the git hooks report (a guard denies the flag anyway).
  3. Verify. pnpm verify must pass. Fix at the source; never open a PR over a red gate.
  4. Push. git push -u origin <branch> with the name spelled out, or git push -u origin HEAD; the guard denies a target held in a shell variable ("$BRANCH"). Add --force-with-lease only if the branch was rebased and the user knows.
  5. Body. Read .github/PULL_REQUEST_TEMPLATE.md and fill it: a one- or two-sentence Summary of what changed and why, the three-place-sync boxes ticked only for what this PR did (source and tests, spec, decision record, or N/A), the docs-hygiene boxes ticked only after the commands ran, and reviewer notes covering how it was checked (the gate commands that ran), risks, and follow-ups. If an issue number was given, add Closes #<n> under Summary.
  6. Create. gh pr create --base <default branch> --title "<conventional subject>" --body-file <the filled body>. The title is the branch's headline commit subject, or a Conventional Commit summary of the set.
  7. Report the PR URL and what CI will run. Then stop: watching checks (gh pr checks) or fixing a red run is a separate ask.

If the request names the issue to close or the PR title, use them.

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