agentleFS
Sign inStart free
rpraharajrpraharaj/ai-sdlc/skills/open-pr/SKILL.md

open-pr

Skill0 starsChanged 17 days agoMITView on GitHub

Open a pull request for the current branch with summary, risk, and test plan. Use when the user wants a PR, merge request, or to send work for review. Use the host CLI if authenticated; otherwise print the body and push instructions.

62 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use commit-push, address-review and 5 more.

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.
  • DataCoveySkill

    commit-push

    Commit and push the changes made on this chat session to the current branch. Use best practices from Conventional Commits.

    Also in 3 projects that use this

  • saffron-healthSkill

    address-review

    Address PR review comments systematically. Use when responding to code review feedback on a pull request.

    Also in 3 projects that use this

  • DockerSkill

    review-pr

    Review one or more incoming Docker documentation pull requests as a maintainer. Independently validate technical claims, assess editorial fit and information architecture, choose a verdict, and draft exact inline or PR-wide feedback behind a confirmation gate. Use for requests such as "review PR 123", "is this PR correct?", "does this information belong here?", "validate this PR", or "help review backlog PRs". Do not use to maintain or fix a PR you own; use maintain-pr for that.

    Also in 10 projects that use this

  • HashiCorpSkill

    changelog

    Add a `.changelog/<PR_NUMBER>.txt` entry for a GitHub Pull Request, commit, and push.

    Also in 5 projects that use this

  • Google CloudSkill

    fix

    Plan a remediation strategy after a test failure.

    Also in 3 projects that use this

  • Harut8Skill

    architect

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 61 edited versions we read keep these.

  • 2

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

    Write the body from the diff using references/pr-template.md, or the repo’s PR template if it exists.

    line 42
  2. Distinctive:

    If the existing host CLI is authenticated: push and create.

    line 44

“Common” is measured: kept by at least 6 in 10 of the 61 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

Open PR

Publish the current branch for review. Do not merge.

Is this the right skill?

SignalDo this instead
Uncommitted work they want in the PRcommit first
On default branchstop unless they insisted
No commits vs basestop

Required inputs

  • git and commits on this branch vs the default base
  • The authenticated git-host CLI this repo already uses if they want it created remotely

Human decisions (do not invent)

  • Merge
  • Force-push
  • Reviewers (only if they named them)

Procedure

  1. Inspect branch, status, remote, log. Detect base (main / master / trunk / remote HEAD).
  2. Say if ready-to-merge was not run; do not block unless they asked for a merge gate.
  3. Write the body from the diff using references/pr-template.md, or the repo’s PR template if it exists.
  4. Title matches this repo’s PR style if you can see past PRs; else commit style.
  5. If the existing host CLI is authenticated: push and create. Else push only if they asked, then print title, body, base, and compare URL. No force-push to a shared branch.

Output

  • Path: PR/MR URL or printed body
  • Template: references/pr-template.md

Quality bar

  • Body is from the diff
  • Test plan lists commands you ran or steps
  • Not merged

Done

URL or printed body. List which test-plan items you actually ran.

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