원클릭으로 Manus에서 모든 스킬 실행

create-pr

스타4

포크0

업데이트2026년 3월 17일 08:48

Creates a GitHub pull request for the current branch using the gh CLI. Use when asked to create a PR, open a pull request, submit changes for review, or push and create a PR. Defaults to draft, detects and fills repo PR templates, auto-detects the base branch, and supports 'ready for review' override. DO NOT TRIGGER for reviewing existing PRs or commenting on PRs.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

shousper

shousper/claude-kit

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Create Pull Request

Overview

Create a pull request for the current branch. Defaults to draft so the author can review on GitHub before marking ready.

Core principle: Draft by default. The author controls when a PR is ready for review.

The Process

Step 1: Check Prerequisites

# Verify gh CLI is available and authenticated
command -v gh >/dev/null 2>&1 || echo "GitHub CLI (gh) not installed"
gh auth status 2>/dev/null || echo "Not authenticated with gh"

# Detect default branch
base=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@')
base=${base:-main}
git log "origin/$base..HEAD" --oneline

# Verify branch is pushed
git rev-parse --abbrev-ref --symbolic-full-name @{u} 2>/dev/null

If branch is not pushed:

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

Step 2: Detect PR Template

# Check common template locations
ls .github/PULL_REQUEST_TEMPLATE.md 2>/dev/null
ls .github/PULL_REQUEST_TEMPLATE/ 2>/dev/null
ls docs/PULL_REQUEST_TEMPLATE.md 2>/dev/null
ls PULL_REQUEST_TEMPLATE.md 2>/dev/null

If template exists: read it, fill out all sections from diff and commit history. If no template: examine recent merged PRs for conventions (gh pr list --state merged --limit 5).

Step 3: Create the PR

Default (draft):

gh pr create --draft --title "<title>" --body "<body>"

If your human partner explicitly requests "ready for review":

gh pr create --title "<title>" --body "<body>"

PR Content

Title: Short (under 70 chars), describes the change

Body: If using template, fill all sections. If no template:

## Summary
<2-3 bullets of what changed and why>

## Test Plan
- [ ] <verification steps>

Draft Override

Your human partner can request a non-draft PR by saying:

"ready for review"
"skip draft"
"mark it ready"
"not a draft"

In these cases, omit the --draft flag.

Common Mistakes

Hardcoding main as the base branch — always detect the default branch dynamically; some repos use master, develop, or other names.
Creating the PR before pushing the branch — gh pr create will fail if the branch doesn't exist on the remote.
Skipping the PR template — if the repo has one, fill it out completely. Reviewers expect it.
Writing vague titles — "Update code" or "Fix stuff" tells reviewers nothing. Describe the actual change.
Forgetting --draft — the default is draft for a reason. Only omit when your human partner explicitly asks.

Integration

Called by:

finish-branch (Option 2) — after committing and pushing
User directly by asking to create a PR (triggers via description match)

References:

Installed /commit command for staging and committing

이 저장소의 다른 Skills

같은 저장소

build-flow

shousper/claude-kit

The default vehicle for implementing a coherent batch of code changes — a feature, refactor, bug fixes, or remediation from an audit/review — via a background TDD workflow with an independent spec+quality review gate and staged fix-loop (pausing only when blocked). Use it the moment you are about to edit source files for such a batch, whether the plan came from kit:writing-plans, a docs/plans/*.md file, an audit/analysis you just ran, or asks like "execute the plan", "implement this", "do the refactor", or "remediate the findings" — even for small batches. In ultracode mode, implement via build-flow rather than hand-editing or a one-off workflow. DO NOT TRIGGER for a new feature with no design yet (use kit:brainstorming first), for pure analysis/research/review that changes no code (author a plain workflow), or for a single trivial edit.

2026-07-014

brainstorming

shousper/claude-kit

Coordinates collaborative design sessions that explore requirements, analyze codebase context, and produce an approved design document with trade-offs. Use when building a new feature, adding functionality, creating components, modifying behavior, starting a project, or planning any creative work. DO NOT TRIGGER when the user already has a concrete design and just wants implementation.

2026-06-174

code-review

shousper/claude-kit

Orchestrates plan-alignment and quality review via a bundled review workflow that fans out review dimensions (correctness, quality, tests, security, architecture) and adversarially verifies each finding. Use when verifying implementation matches requirements or design/architectural alignment, before merging to main, after completing a major feature, before refactoring, after fixing a complex bug, or when a fresh perspective is needed. Consolidates findings into one report.

2026-06-174

finish-branch

shousper/claude-kit

Finalizes a development branch by verifying tests pass, then presenting four completion options (merge locally, draft PR, keep as-is, or discard). Use when implementation is done, a feature branch is ready to ship, work needs to be merged or a PR created, or the user says "finish", "wrap up", "ship it", or "done with this branch". DO NOT TRIGGER when tests are still being written or implementation is incomplete.

2026-06-174

git-worktrees

shousper/claude-kit

Creates an isolated git worktree workspace with smart directory selection, gitignore safety verification, dependency installation, and baseline test validation. Use when starting feature work, beginning a new branch, needing workspace isolation, setting up before plan execution, or the user says "new feature", "set up a worktree", or "isolate this work". DO NOT TRIGGER for worktree cleanup or removal — use kit:worktree-cleanup instead.

2026-06-174

using-kit

shousper/claude-kit

Enforces skill discovery and invocation governance for every task. Use at the start of any conversation, before responding to any user message, when deciding whether a skill applies, when building or modifying features (triggers the brainstorming chain), or when operating within a team context. Defines the default workflow chain (brainstorming -> writing-plans -> build-flow -> finish-branch) and prevents rationalizing away skill usage.

2026-06-174

name	create-pr
description	Creates a GitHub pull request for the current branch using the gh CLI. Use when asked to create a PR, open a pull request, submit changes for review, or push and create a PR. Defaults to draft, detects and fills repo PR templates, auto-detects the base branch, and supports 'ready for review' override. DO NOT TRIGGER for reviewing existing PRs or commenting on PRs.

Create Pull Request

Overview

Create a pull request for the current branch. Defaults to draft so the author can review on GitHub before marking ready.

Core principle: Draft by default. The author controls when a PR is ready for review.

The Process

Step 1: Check Prerequisites

# Verify gh CLI is available and authenticated
command -v gh >/dev/null 2>&1 || echo "GitHub CLI (gh) not installed"
gh auth status 2>/dev/null || echo "Not authenticated with gh"

# Detect default branch
base=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@')
base=${base:-main}
git log "origin/$base..HEAD" --oneline

# Verify branch is pushed
git rev-parse --abbrev-ref --symbolic-full-name @{u} 2>/dev/null

If branch is not pushed:

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

Step 2: Detect PR Template

# Check common template locations
ls .github/PULL_REQUEST_TEMPLATE.md 2>/dev/null
ls .github/PULL_REQUEST_TEMPLATE/ 2>/dev/null
ls docs/PULL_REQUEST_TEMPLATE.md 2>/dev/null
ls PULL_REQUEST_TEMPLATE.md 2>/dev/null

If template exists: read it, fill out all sections from diff and commit history. If no template: examine recent merged PRs for conventions (gh pr list --state merged --limit 5).

Step 3: Create the PR

Default (draft):

gh pr create --draft --title "<title>" --body "<body>"

If your human partner explicitly requests "ready for review":

gh pr create --title "<title>" --body "<body>"

PR Content

Title: Short (under 70 chars), describes the change

Body: If using template, fill all sections. If no template:

## Summary
<2-3 bullets of what changed and why>

## Test Plan
- [ ] <verification steps>

Draft Override

Your human partner can request a non-draft PR by saying:

"ready for review"
"skip draft"
"mark it ready"
"not a draft"

In these cases, omit the --draft flag.

Common Mistakes

Hardcoding main as the base branch — always detect the default branch dynamically; some repos use master, develop, or other names.
Creating the PR before pushing the branch — gh pr create will fail if the branch doesn't exist on the remote.
Skipping the PR template — if the repo has one, fill it out completely. Reviewers expect it.
Writing vague titles — "Update code" or "Fix stuff" tells reviewers nothing. Describe the actual change.
Forgetting --draft — the default is draft for a reason. Only omit when your human partner explicitly asks.

Integration

Called by:

finish-branch (Option 2) — after committing and pushing
User directly by asking to create a PR (triggers via description match)

References:

Installed /commit command for staging and committing