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

pr-creation

스타8

포크1

업데이트2026년 6월 8일 08:25

Create (draft) pull requests on GitHub. Use when user requests to create a pr, pull request, draft pr, draft pull request.

설치

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

Manus에서 실행

출처

thomasmol

thomasmol/opencode-config

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

다운로드

Manus에서 실행

What I do

Create a draft pull request using GitHub CLI. Assume code is done. Do not make code changes, format changes, config changes, commits, branch changes, or push changes when this skill is active.

Workflow

Run only minimal git/GitHub CLI checks needed for PR creation.

Check current branch.

git branch --show-current

Stop if current branch is main, master, staging, production, or repo default branch. Inform user PR cannot be created from default/protected branch. Suggest creating a feature branch from committed work.

Check repo default branch.

gh repo view --json defaultBranchRef --jq .defaultBranchRef.name

Use this branch as PR base unless user specified another base.

Check uncommitted changes.

git status --porcelain

Stop if output is non-empty. Inform user uncommitted changes exist. Ask whether they want to commit/stash/discard manually before PR creation.

Check unpushed commits/upstream state.

git status -sb

Stop if output shows ahead commits, no upstream, or branch not pushed. Inform user branch must be pushed before PR creation. Suggest git push -u origin <current-branch>.

Inspect diff against base branch for PR title/body only.

git fetch origin
git diff --stat origin/<base-branch>...HEAD
git diff origin/<base-branch>...HEAD

Use diff and branchname to create specific title/body. Do not edit files.

Create draft PR.

gh pr create --draft --base <base-branch> --title "feature: specific title" --body $'- Specific change with file/method/class references\n- Another specific change\n\nCloses ISSUE_ID'

PR content rules

Title prefix must match change type: feature:, fix:, chore:, refactor:, docs:.
Body must be specific. Mention relevant files, methods, classes, behavior changes.
Do not add generic headings like Draft PR, Changes made, or Summary.
Link Linear issues with Closes ISSUE_ID ISSUE_ID_2 when issue ids are provided or extractable from branch name.
Ask for issue ids only if user asked to link issue ids but none are provided or extractable.
Return created draft PR URL.

When to use me

Use when user requests creating a PR, pull request, draft PR, or draft pull request for already-finished work.

이 저장소의 다른 Skills

같은 저장소

review-comments

thomasmol/opencode-config

Pull GitHub PR review comments for current branch or provided PR number, inspect code, and produce update plan. Use for PR feedback, requested changes, reviewer comments, or plan fixes from review comments.

2026-07-098

agent-browser

thomasmol/opencode-config

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality.

2026-04-258

thomasmol/opencode-config

Explore, build, and refine UI using the Tailwind Labs ui.sh mcp

2026-04-098

linear

thomasmol/opencode-config

Create, read, update, and list Linear issues. Use when user requests to create, read, update, or list Linear projects, issues, tickets, or tasks.

2026-03-088

name	pr-creation
description	Create (draft) pull requests on GitHub. Use when user requests to create a pr, pull request, draft pr, draft pull request.

What I do

Create a draft pull request using GitHub CLI. Assume code is done. Do not make code changes, format changes, config changes, commits, branch changes, or push changes when this skill is active.

Workflow

Run only minimal git/GitHub CLI checks needed for PR creation.

Check current branch.

git branch --show-current

Check repo default branch.

gh repo view --json defaultBranchRef --jq .defaultBranchRef.name

Use this branch as PR base unless user specified another base.

Check uncommitted changes.

git status --porcelain

Stop if output is non-empty. Inform user uncommitted changes exist. Ask whether they want to commit/stash/discard manually before PR creation.

Check unpushed commits/upstream state.

git status -sb

Stop if output shows ahead commits, no upstream, or branch not pushed. Inform user branch must be pushed before PR creation. Suggest git push -u origin <current-branch>.

Inspect diff against base branch for PR title/body only.

git fetch origin
git diff --stat origin/<base-branch>...HEAD
git diff origin/<base-branch>...HEAD

Use diff and branchname to create specific title/body. Do not edit files.

Create draft PR.

gh pr create --draft --base <base-branch> --title "feature: specific title" --body $'- Specific change with file/method/class references\n- Another specific change\n\nCloses ISSUE_ID'

PR content rules

Title prefix must match change type: feature:, fix:, chore:, refactor:, docs:.
Body must be specific. Mention relevant files, methods, classes, behavior changes.
Do not add generic headings like Draft PR, Changes made, or Summary.
Link Linear issues with Closes ISSUE_ID ISSUE_ID_2 when issue ids are provided or extractable from branch name.
Ask for issue ids only if user asked to link issue ids but none are provided or extractable.
Return created draft PR URL.

When to use me

Use when user requests creating a PR, pull request, draft PR, or draft pull request for already-finished work.