agentleFS
kimrgreykimrgrey/claudini/.claude/skills/create-pull-request/SKILL.md

create-pull-request

Skill9 starsChanged 9 months agoMITView on GitHub

Create a new branch, commit all changes, push, and open a PR.

  • Commits and pushes

27 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use grilling and frontend-design.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • GoogleSkill

    grilling

    Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

    Also in 3 projects that use this

  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 27 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Commit, push, and open a PR.

    line 8
  2. Distinctive:

    Stage and commit: all changes

    line 19
  3. Distinctive:

    Write a concise commit message (1-2 sentences) focusing on the "why"

    line 21
  4. Distinctive:

    Follow all Git & PR conventions from CLAUDE.md

    line 32
  5. Distinctive:

    Never add Claude as a co-author

    line 34
  6. Distinctive:

    Always assign the PR to its author

    line 35

“Common” is measured: kept by at least 6 in 10 of the 27 edited versions of this file we could read. “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

Create Pull Request

Commit, push, and open a PR.

Context

Current branch: !git branch --show-current Working tree status: !git status --short

Steps

  1. Create a new branch from the current branch
    • Pick a short, readable name describing the changes
  2. Stage and commit all changes
    • Stage specific files — never use git add -A or git add .
    • Write a concise commit message (1-2 sentences) focusing on the "why"
  3. Push the branch with -u origin <branch>
  4. Open a PR with gh pr create
    • Title under 70 characters
    • Short summary in the body
    • Assign to @me
  5. Stop here — return the PR URL to the user

Rules

  • Do not merge unless the user explicitly asks to merge — if asked, use the merge-pull-request skill
  • Follow all Git & PR conventions from CLAUDE.md
  • Never force push
  • Never add Claude as a co-author
  • Always assign the PR to its author

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.