agentleFS
Sign inStart free
lfrodrigueslfrodrigues/packt-claude-code-course-auth/.claude/skills/pr/SKILL.md

pr

Skill9 starsChanged 4 months agoMITView on GitHub

Open a PR for the current branch using the plan file as context

  • Commits and pushes

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
  • could be automatic: a setting could enforce it
  1. Very specific:

    Run gh pr create with the drafted title/body.

    line 20
  2. Distinctive:

    Do NOT open a PR against main/master from main/master itself, and do NOT force-push to get there.

    line 27
  3. Distinctive:

    NOT force-push to get there.

    line 28
  4. Very specific:

    Do NOT fabricate a plan or verification section if none exists — if the branch has commits with no Plan: trailer, stop and say so.

    line 29

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

Additional context: $ARGUMENTS

  1. Confirm the branch is pushed and is not main/master (git rev-parse --abbrev-ref HEAD; if unpushed, push it first as /ship does — do not force-push).
  2. Find the plan(s) behind this branch: git log main..HEAD --grep='^Plan:' (or the equivalent base branch). Read the referenced docs/plans/NNN-*.md file(s) for the Context/Approach/Verification content.
  3. Draft the PR title (concise, imperative) and body from that plan content — not a generic diff summary. Include a "Verification" section describing what was actually run (from the plan's own verification section).
  4. Run gh pr create with the drafted title/body. Use the repo's .github/pull_request_template.md structure if the repo has one and the drafted content doesn't already follow it.
  5. Print the PR URL.

Policy:

  • Do NOT open a PR against main/master from main/master itself, and do NOT force-push to get there.
  • Do NOT fabricate a plan or verification section if none exists — if the branch has commits with no Plan: trailer, stop and say so; that shouldn't be possible given the commit-msg hook, but don't paper over it if it happens.
  • This command only opens the PR; it does not merge it.

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