git-open-pr

스타14

포크9

업데이트2026년 7월 29일 15:25

Draft well-structured Pull Request titles and descriptions. Use whenever the user wants to open a PR, write a pull request, draft a PR description, or prepare a PR for review — also when they give a ticket ID or branch name alongside code changes without saying "pull request".

설치

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

출처

nmnhut

nmnhut/fit-summer-school-2026

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

다운로드

Open PR

Draft and open Pull Requests following the workspace conventions.

Format

Title: <ticket-id>: <short summary> — e.g. DEMO-101: Block closing tasks with pending scans.
Target: main unless stated otherwise; if unclear, ask — don't guess.
Body: one or two sentences plus a tight bullet list of key changes — don't enumerate files. Add a ## Side task section only for minor, loosely-related out-of-scope changes.

<!-- One or two sentences: what this PR does and why. -->

- <key change>

## Side task *(optional)*
<!-- Minor, loosely-related out-of-scope changes only. -->

Decision rules

Keep changes within the ticket. Don't fix unrelated issues — even pre-existing ones — note them instead; an unavoidable minor related change goes under ## Side task.
New endpoints or processing paths need test coverage before the PR.

Workflow

Collect inputs — target branch, ticket ID, a brief description, and any side tasks.
Draft title + body in the format above; omit empty sections; keep it tight.
Present the title and body in a copyable block; iterate on feedback and confirm before opening. A person merges — the agent never merges.

Open with the GitHub CLI, passing the body via a file:

gh pr create --base <target-branch> --title "<title>" --body-file <file>.md

Writing multi-line bodies (commit or PR)

Never pass a multi-line message as an inline quoted string with \n escapes — the shell does not expand \n, so literal \n ends up in the PR. Use a file or a heredoc:

gh pr create --body-file body.md   # not: --body "line1\nline2"

Example

DEMO-101: Block closing tasks with pending scans

Prevent a task from being closed while its attachment scan is still pending.

- Added a close-guard check against the scan status in the task service
- Returned 409 with a user-facing message when the scan is pending
- Functional test against the scan simulator

## Side task
- Fixed a typo in the task-board column header noticed while testing.

이 저장소의 다른 Skills

같은 저장소

coding-convention

nmnhut/fit-summer-school-2026

Python coding conventions for this workspace. Use when writing or reviewing Python in taskflow-api or scan-simulator — apply automatically, without asking for confirmation.

2026-07-2914

git-commit

nmnhut/fit-summer-school-2026

Use when suggesting a commit message, branching, staging, committing, merging, resolving conflicts, or pushing in any project of this workspace.

2026-07-2914

implement-feature

nmnhut/fit-summer-school-2026

Multi-step pipeline that takes a ticket from research to PR — research → spec → code → review + test → PR. Use for any ticket in agent-hub/tickets/.

2026-07-2914

release-note

nmnhut/fit-summer-school-2026

Draft a release note from recent commits/closed tickets. Used in Part 2 of the session as the "simple skill" example.

2026-07-2914

route-to-flow

nmnhut/fit-summer-school-2026

Answer "what code implements this?" from a ticket, spec, or plain question — returns the registered call chain from the flow registry plus the impact of changing it.

2026-07-2914

name	git-open-pr
description	Draft well-structured Pull Request titles and descriptions. Use whenever the user wants to open a PR, write a pull request, draft a PR description, or prepare a PR for review — also when they give a ticket ID or branch name alongside code changes without saying "pull request".

Open PR

Draft and open Pull Requests following the workspace conventions.

Format

Title: <ticket-id>: <short summary> — e.g. DEMO-101: Block closing tasks with pending scans.
Target: main unless stated otherwise; if unclear, ask — don't guess.
Body: one or two sentences plus a tight bullet list of key changes — don't enumerate files. Add a ## Side task section only for minor, loosely-related out-of-scope changes.

<!-- One or two sentences: what this PR does and why. -->

- <key change>

## Side task *(optional)*
<!-- Minor, loosely-related out-of-scope changes only. -->

Decision rules

Keep changes within the ticket. Don't fix unrelated issues — even pre-existing ones — note them instead; an unavoidable minor related change goes under ## Side task.
New endpoints or processing paths need test coverage before the PR.

Workflow

Collect inputs — target branch, ticket ID, a brief description, and any side tasks.
Draft title + body in the format above; omit empty sections; keep it tight.
Present the title and body in a copyable block; iterate on feedback and confirm before opening. A person merges — the agent never merges.

Open with the GitHub CLI, passing the body via a file:

gh pr create --base <target-branch> --title "<title>" --body-file <file>.md

Writing multi-line bodies (commit or PR)

Never pass a multi-line message as an inline quoted string with \n escapes — the shell does not expand \n, so literal \n ends up in the PR. Use a file or a heredoc:

gh pr create --body-file body.md   # not: --body "line1\nline2"

Example

DEMO-101: Block closing tasks with pending scans

Prevent a task from being closed while its attachment scan is still pending.

- Added a close-guard check against the scan status in the task service
- Returned 409 with a user-facing message when the scan is pending
- Functional test against the scan simulator

## Side task
- Fixed a typo in the task-board column header noticed while testing.