agentleFS
insapption-projectsinsapption-projects/claude-agent-team-starter/.claude/skills/create-pr/SKILL.md

create-pr

Skill1 starsChanged 8 months agoMITView on GitHub

Pushes the current branch to remote and creates a pull request with a structured description including what changed, why, how to test, and relevant screenshots. Step 6 of the dev-workflow.

  • Reads credentials
  • 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

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

  • 0

    Common

    Most of the 179 edited versions we read keep these.

  • 3

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

    All changes must be committed (Step 5 completed)

    line 19
  2. Distinctive:

    If working tree is dirty, stop and report:

    line 33
  3. Very specific:

    Check php artisan test --filter ProductFilterTest — should be green

    line 95
  4. Distinctive:

    Use GitHub CLI if available:

    line 115
  5. Very specific:

    If gh is not available, output the PR body for manual submission and provide the GitHub URL for the branch:

    line 125

“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

Skill: /create-pr

Usage

/create-pr "{task_description}"

Prerequisites

  • All changes must be committed (Step 5 completed)
  • Branch must not already have an open PR

Steps

1. Pre-flight Check

git status          # must be clean (nothing to commit)
git log main..HEAD  # show commits to be included in PR

If working tree is dirty, stop and report:

🚧 STOP: Uncommitted changes detected. Run /git-commit first.

2. Push to Remote

git push -u origin $(git branch --show-current)

Confirm:

✅  Pushed to origin/{branch-name}

3. Generate PR Description

Compose the full PR using this template. Fill every section with real content — do NOT leave any section as a placeholder.


PR Title: {type}({domain}): {imperative description} (≤ 72 chars)


## Summary

One paragraph explaining what this PR does and the business reason for it.

## Changes

A clear list of every changed file and what changed, grouped by layer:

Backend (Laravel)

  • app/Services/ProductFilterService.php — new service for product filtering
  • app/Http/Controllers/ProductController.php — inject filter service, update index()

Frontend (React)

  • src/hooks/useProductFilter.ts — new React Query hook wrapping filter API
  • src/components/ProductFilter/ProductFilter.tsx — new filter UI component

Database

  • database/migrations/..._add_category_id_to_products.php — adds category_id FK

Docs / Reference

  • references/backend_map.md — updated with ProductFilterService
  • references/frontend_map.md — updated with useProductFilter hook

## How to Test

Step-by-step instructions for a reviewer to manually verify the change:

  1. php artisan migrate to run the new migration
  2. Navigate to /products → filter panel should appear in the sidebar
  3. Select a category → list should update without page reload
  4. Clear filter → all products should reappear
  5. Check php artisan test --filter ProductFilterTest — should be green

## Screenshots (UI changes only)

BeforeAfter
(describe or attach)(describe or attach)

## Checklist

  • Tests pass (php artisan test / pnpm test)
  • Lint passes (no errors)
  • Reference files updated (references/*.md)
  • No .env values committed
  • No debug code (dd(), console.log) left in

4. Open the PR

Use GitHub CLI if available:

gh pr create \
  --title "{PR title}" \
  --body "{PR body}" \
  --base main \
  --head $(git branch --show-current)

If gh is not available, output the PR body for manual submission and provide the GitHub URL for the branch:

🔗 Manual PR creation required.
   Branch URL: https://github.com/{org}/{repo}/compare/{branch-name}
   Copy the PR body above.

5. Confirm

──────────────────────────────────────────────────────────────
  PULL REQUEST CREATED
──────────────────────────────────────────────────────────────
PR URL    : {url}
Title     : {title}
Base      : main
Head      : {branch}
Commits   : {count}

Next step: /test-lint {technology}
──────────────────────────────────────────────────────────────

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.