agentleFS
ClickHouseClickHouse/clickhouse-connect/.claude/skills/create-pr/SKILL.md

create-pr

Skill536 starsChanged 4 days agoApache-2.0View on GitHub

Draft a PR title and summary following the repo's pull request template, and open the PR if asked. Use when the user wants a PR description written, or wants to open a PR.

  • Commits and pushes

196 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use update-pr, create-release-note 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 10 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

  • 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

  • +1 more from microsoft

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 179 edited versions we read keep these.

  • 7

    Distinctive

    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
  1. Very specific:

    Write a PR for the current branch following .github/pull_request_template.md.

    line 8
  2. Distinctive:

    Look at git log main..HEAD and git diff main...HEAD to see what actually changed.

    line 12
  3. Distinctive:

    No filler, no LLM stock phrases, no restating the obvious.

    line 19
  4. Distinctive:

    Use simple words, simple explanations, and simple sentence structure.

    line 20
  5. Distinctive:

    If the PR closes or relates to an open issue, link it as the template asks.

    line 22
  6. Distinctive:

    Keep the checklist from the template as-is, checking off what applies and deleting items that don't, per the template's own instruction.

    line 26
  7. Distinctive:

    Default to drafting only: print the title and body in a fenced block and stop.

    line 30
  8. Distinctive:

    Only push and open the PR if the user's request makes that clear (e.g.

    line 32
  9. Very specific:

    Run gh pr create --title "..." --body "..." with the drafted content.

    line 34

“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

Write a PR for the current branch following .github/pull_request_template.md.

1. Understand the change

Look at git log main..HEAD and git diff main...HEAD to see what actually changed. Base the summary on the real diff, not just commit messages.

2. Write the summary

  • Provide a terse and concise summary.
  • Plain, simple language. Explain what changed and why, the way you'd explain it to a teammate, not a changelog entry.
  • Short, natural sentences. No em dashes, en dashes, or semicolons. Avoid parentheses where possible.
  • No filler, no LLM stock phrases, no restating the obvious.
  • Use simple words, simple explanations, and simple sentence structure. A human should be easily able to parse and understand the writing.
  • Don't mention that tests, linting, or type checks were run. That's assumed for anything going into a PR. Only call out testing or validation if it's actually central to what the PR is about (e.g. it's the thing being fixed or added).
  • If the PR closes or relates to an open issue, link it as the template asks. Don't include the . at the end of the Closes #NNN.

3. Fill out the checklist

Keep the checklist from the template as-is, checking off what applies and deleting items that don't, per the template's own instruction.

4. Draft vs. open

Default to drafting only: print the title and body in a fenced block and stop.

Only push and open the PR if the user's request makes that clear (e.g. "open a PR", "create the PR", "submit it"). In that case:

  • Push the branch if it isn't already pushed (git push -u origin <branch>).
  • Run gh pr create --title "..." --body "..." with the drafted content.
  • Print the resulting PR URL.

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.