agentleFS
genlayerlabsgenlayerlabs/genlayer-studio/.claude/skills/create-pr/SKILL.md

create-pr

Skill180 starsChanged 8 months agoMITView on GitHub

Create GitHub pull requests by analyzing branch diff and following the project template

  • 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, 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

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

  • 0

    Common

    Most of the 179 edited versions we read keep these.

  • 2

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

    Create GitHub pull requests by analyzing branch diff and following the project template.

    line 8
  2. Very specific:

    Use gh pr create with the project template structure:

    line 44
  3. Distinctive:

    Keep PR title under 72 characters

    line 119

“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 Pull Request Skill

Create GitHub pull requests by analyzing branch diff and following the project template.

Prerequisites

  • On a feature branch (not main)
  • Changes committed locally
  • GitHub CLI (gh) authenticated

Workflow

1. Gather Context

# Get current branch name
git branch --show-current

# Check if branch is pushed
git status

# Get diff against main
git diff main...HEAD --stat
git diff main...HEAD

# Get commit history for this branch
git log main..HEAD --oneline

2. Analyze Changes

Review the diff to understand:

  • What: Files changed, functions modified, features added/removed
  • Why: The purpose behind the changes (bug fix, feature, refactor)
  • Testing: What tests were added or should be run

3. Create PR

Use gh pr create with the project template structure:

gh pr create --title "<type>: <description>" --body "$(cat <<'EOF'
Fixes #issue-number-here

# What

- [Describe specific changes made]
- [List modified components/files]

# Why

- [Explain the motivation]
- [Reference related issues]

# Testing done

- [List tests run]
- [Describe manual testing]

# Decisions made

- [Document any non-obvious choices]

# Checks

- [x] I have tested this code
- [x] I have reviewed my own PR
- [ ] I have created an issue for this PR
- [x] I have set a descriptive PR title compliant with conventional commits

# Reviewing tips

- [Guidance for reviewers]

# User facing release notes

- [Changes visible to end users, if any]
EOF
)"

Conventional Commit Types

TypeUse Case
featNew feature
fixBug fix
docsDocumentation only
styleFormatting, no code change
refactorCode change, no feature/fix
perfPerformance improvement
testAdding/fixing tests
choreMaintenance, deps, config

Examples

Feature PR

gh pr create --title "feat: add user authentication" --body "..."

Bug Fix PR

gh pr create --title "fix: resolve timeout in consensus worker" --body "..."

With Issue Link

gh pr create --title "fix: handle empty contract data" --body "Fixes #123..."

Tips

  • Keep PR title under 72 characters
  • Reference issue numbers with Fixes #N or Closes #N for auto-close
  • For WIP, use gh pr create --draft
  • Push branch first if needed: git push -u origin $(git branch --show-current)

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.