agentleFS
lohi-ailohi-ai/babysit/.claude/skills/create-pr/SKILL.md

create-pr

Skill0 starsChanged 7 days agoMITView on GitHub

Prepare and create a pull request from the current branch. Use when a human requests a PR; 2build workflows never open one.

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

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

  • 0

    Common

    Most of the 179 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    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:

    Create a reviewable PR without merging it.

    line 7
  2. Very specific:

    If origin/<base_branch> has moved, sync it the way the human asks.

    line 12
  3. Distinctive:

    Do not include unrelated working-tree changes.

    line 23
  4. Distinctive:

    Do not claim checks passed unless they ran.

    line 24
  5. Distinctive:

    Do not merge; landing and deployment are outside this skill.

    line 25
  6. Distinctive:

    If authentication or remote configuration is missing, emit exact setup guidance.

    line 26

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

Create a reviewable PR without merging it.

Flow

  1. Inspect git status, branch, commits, and remote. The PR targets the base branch (BBS_BASE_BRANCH → bbs config get base_branch → origin/HEAD → main). The current branch is the PR source; if it is the base there is nothing to PR (BLOCKED, naming git switch -c <branch> as the fix), and if it carries other work, say so in the PR body. Load repo env: eval "$(bbs secrets load | sed -E '/^export CLOUDFLARE_(ACCOUNT_ID|API_TOKEN)=/d')"; if GH_ACCOUNT is set, gh auth switch -u "$GH_ACCOUNT" before any push or gh pr call (multi-account machines fail with "Repository not found" on the wrong account).
  2. Read requirement, plan, implementation handoff, and verification evidence when present. Carry them into the PR body as a short reviewer explainer: context and intent, where new code meets existing behavior, deviations from the plan (implement handoff's ## Deviations), QA evidence. Highlight any consequential interpretation, system impact or unresolved assumption the reviewer must judge. Include prototype/QA links when relevant; no mandatory quiz or repeated plan.
  3. Resolve mechanical version or changelog requirements only when the repo requires them.
  4. If origin/<base_branch> has moved, sync it the way the human asks; syncing changes the tested state: rerun affected checks before claiming current verification. Commit only remaining intended changes. For a resolved ticket, inspect bbs ticket readiness --action pr --json and require data.ready=true for the final head. Then push the source branch and open the PR against base_branch. When a ticket resolves, persist bbs ticket set-pointer pr <url> and bbs ticket set-status in_review. board --pr uses the pointer; status becomes done only after the PR is observed merged.
  5. Return the PR URL, title, summary, tests, and concerns. Cross-repo tickets: a sibling repo's change needs its own create-pr run there; list the sibling repo + branch in the summary instead of fanning out.

Rules

  • Never force-push.
  • Do not include unrelated working-tree changes.
  • Do not claim checks passed unless they ran.
  • Do not merge; landing and deployment are outside this skill.
  • If authentication or remote configuration is missing, emit exact setup guidance.

Output

STATUS: DONE | DONE_WITH_CONCERNS | NEEDS_CONTEXT | BLOCKED
VERDICT: PR_CREATED
PR: <url>
SUMMARY: <title + checks>
NEXT: human review

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.