agentleFS
phmatrayphmatray/ai-migration-kit/skills/create-pr/SKILL.md

create-pr

Skill4 starsChanged 59 days agoMITView on GitHub

Open a pull request for a finished feature branch — or a fix left on the default branch itself (debug-issue's hand-off), which this skill branches off first: push it through the guard, link its issue, gate the title, and open it ready when the full test passes (a draft when asked, or when the test is red). Triggers: "open a PR for this branch", "create a pull request for my fix", "turn this branch into a PR", "I just fixed the flaky test on main, open a PR for it", « ouvre une PR pour ce correctif », « crée la pull request », « le correctif est commité, ouvre la PR ». Does NOT apply to merging a PR (merge-pr), building a planned issue (implement-issue), reviewing a diff (code-review), or filing an issue (create-issue).

196 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use update-pr, act-on-feedback and 10 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.
  • MicrosoftSkill

    update-pr

    Update the pull request for the current session. Use when the user wants to push new changes to an existing PR.

    Also in 9 projects that use this

  • MicrosoftSkill

    act-on-feedback

    Act on user feedback attached to the current session. Use when the user submits feedback on the session's changes via the Submit Feedback button.

    Also in 3 projects that use this

  • ModelEngine-GroupSkill

    create-release-note

    从 PR/commit 中自动生成结构化的 Release Notes,并可选创建 GitHub Draft Release。支持 x.y.0 版本合并前一 minor 系列的 release notes。当用户要求生成发布说明、创建 release notes 时触发。参数为版本号和可选的上一版本号。

    Also in 3 projects that use this

  • frostneySkill

    native-nostalgia-stack

    Applies the user's FreePascal toolchain and its build, formatting, hook, and test contracts while leaving project-specific mechanics local. Use when scaffolding or working in a FreePascal project that follows this toolchain.

    Also in 3 projects that use this

  • frostneySkill

    software-engineering-excellence

    Applies the user's engineering standards during substantial technical work: preserve scope, use current evidence, delegate independent parts, and complete authorized outcomes. Use during substantial implementation, debugging, refactoring, or multi-part delivery work.

    Also in 3 projects that use this

  • parkchuSkill

    start-mission

    넥스트스텝(NextStep) 미션을 처음 시작할 때, 미션 저장소를 fork·clone하고 최초 작업 브랜치(step1 등)까지 만들어 준다. gh CLI로 fork하고 clone까지 이어서 처리하며, gh가 없거나 인증이 안 돼 있으면 브라우저 Fork 안내로 폴백한다. 이미 fork/clone돼 있으면 재사용하고 이어서 진행한다(재실행 안전). 사용자가 "미션 시작하려는데 저장소 세팅해줘", "새 미션 시작할래", "fork부터 해줘", "/nextstep:start-mission" 등으로 요청할 때 사용한다.

    Also in 3 projects that use this

  • +1 more from microsoft

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 178 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
  1. Distinctive:

    Run hands-off once started.

    line 38
  2. Distinctive:

    Create a task per item and work them in order.

    line 56

“Common” is measured: kept by at least 6 in 10 of the 178 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 a pull request for a finished branch

What this does

implement-issue opens its draft PR before any work lands. A branch built any other way — a fix committed by hand, a spike that turned out right, or a fix debug-issue left sitting on the default branch itself — needs a way to become a PR the way the kit expects. This skill is that way: /create-pr [#<issue>] [--draft] takes the work off the default branch first when that's where it sits, pushes it through the guard, decides ready or draft, and opens the PR through ../_shared/open-pr.md — the one home of the existence lookup, the title gate and the create call. Then it hands off to merge-pr.

Autonomy contract

Run hands-off once started. See ADR 0005 for the decision scope: pick the reasonable default, state the assumption, keep going. Stop only for a genuine blocker:

  • gh not authenticated, or no push rights.
  • A Step 2 refusal — a detached HEAD, a leftover [DEBUG- probe on the default branch, nothing ahead of it, a closed issue. Each one refuses before any write. A dirty tree no longer refuses — Step 2 commits it, through the guard.
  • A PR already open for this branch or its issue: report it, open none.
  • A guard exit that is not a success, or a readback that does not match — including rewind-default.sh's exit 3 (the default is left ahead of origin/$DEFAULT, reported, never retried).

A red Full test is not a blocker. It opens a draft and says why, so nobody merges it by mistake.

Checklist

Create a task per item and work them in order.

  1. Preconditions — profile, gh auth, commit identity.
  2. Locate the work — off the default branch first when that's where it sits, its issue, the refusals and the existing-PR lookup.
  3. Open — guarded push, ready or draft, the body, the shared PR-open recipe, then rewind the default when Step 2 branched off it.
  4. Recap — the shared closing shape (../_shared/recap.md), Next /merge-pr #<pr>.

Resume-safe: a re-run finds the PR an earlier run opened (the recipe's §1) and stops on it.


How to read this skill

One step file at a time, when you reach it — never all up front. Every token loaded here is re-read on every later turn, so the step bodies live under references/steps/. Open a step when its checklist item starts; the shared references it names load the same way.

  • Step 1 — references/steps/01-preconditions.md · reads _shared/preconditions.md
  • Step 2 — references/steps/02-locate-the-work.md · reads _shared/open-pr.md
  • Step 3 — references/steps/03-open.md · reads _shared/open-pr.md, _shared/guard-invocation.md
  • Step 4 — references/steps/04-recap.md · reads _shared/recap.md

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.