ship

Sterne0

Forks0

Aktualisiert24. Juni 2026 um 06:04

Finish the current branch — verify, commit remaining work with the emoji-:: convention, push, and open a PR to develop that passes the PR title check CI. Use when the user says "PR 올려", "출고", "ship", "머지 준비".

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

team-incube

team-incube/Flooding-App-V2

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	ship
description	Finish the current branch — verify, commit remaining work with the emoji-:: convention, push, and open a PR to develop that passes the PR title check CI. Use when the user says "PR 올려", "출고", "ship", "머지 준비".

ship

Take the current branch from "code done" to "PR open" following repo conventions.

Steps

Identify the issue number from the branch name ({type}/{N}-{slug}). If it doesn't contain one, ask the user — the PR title check CI requires (#N).
Verify first: run the verify-loop skill. Do not push failing code.
Commit any remaining changes in Korean, one logical change per commit:
```
{emoji} :: {한국어 요약}
```
Emoji: ✨ feature · ♻️ refactor · 💄 UI/style · 🎨 format · 🐛 bugfix · 🔧 config/CI. Never commit .env.dev/.env.prod or generated *.g.dart/*.freezed.dart files.
Push: git push -u origin {branch}.
Open the PR against develop:
- Title (must match CI regex ^[^ ] :: \(#[0-9]+\) - .+): 🔀 :: (#{N}) - {한국어 제목} Before creating, propose ~3 candidate {한국어 제목} options via AskUserQuestion and let the user pick (or edit) — don't auto-name. The 🔀 :: (#{N}) - prefix is fixed; only the Korean title varies.
- Body: fill .github/PULL_REQUEST_TEMPLATE.md in Korean — 개요, Closes #{N}, 작업내용 (bulleted actual changes), 테스트 방법 (concrete steps), 스크린샷 (placeholder note if UI changed but no screenshot available), 질문사항, 체크리스트 (check only what was actually verified).
- Korean body encoding (Windows/PowerShell): never pipe a here-string into gh ... --body-file - — PowerShell 5.1 encodes native-command stdin in the system codepage and mangles Hangul into ?. Write the body to a UTF-8 file first, then pass its path:
```
gh pr create --base develop --title "🔀 :: (#{N}) - {제목}" --body-file pr_body.md
```
  (Same for gh pr edit --body-file and gh issue create/edit --body-file.) Use the Write tool to create the file (it writes UTF-8), then delete it after. The PR title via --title "..." is fine inline.
Update the issue label to 🌟 Status: Reviewing.
Report the PR URL and the verification results.

Constraints

Base branch is always develop (never main).
Don't merge the PR or enable auto-merge — review is human-gated.
If the branch is behind develop, merge develop in and re-verify before pushing.

Mehr aus diesem Repository

gleiches Repository

start-work

team-incube/Flooding-App-V2

Start work on a GitHub issue — pick or create the issue, then create the convention branch ({type}/{issue}-{slug}) off fresh develop. Use when the user says "이슈 시작", "작업 시작", "start issue", or names an issue number to work on.

2026-06-240

verify-loop

team-incube/Flooding-App-V2

Run the CI-equivalent verification chain (build_runner codegen → flutter analyze → flutter test) and keep fixing + re-running until everything passes. Use before committing, before PRs, or when the user says "검증", "verify", "CI 통과 확인".

2026-06-230

work-loop

team-incube/Flooding-App-V2

Iterative implement → verify → commit cycle on the current branch until the stated goal is done. No branch creation, no PR. Use when the user says "작업 루프", "work loop", or wants heads-down implementation of a defined task list.

2026-06-230

full-loop

team-incube/Flooding-App-V2

Full autonomous cycle for one issue - start-work (issue → branch) → work-loop (implement/verify/commit) → ship (push → PR). Use when the user says "전체 루프", "full loop", "이슈 끝까지", or hands over an issue to complete end-to-end.

2026-06-100

name	ship
description	Finish the current branch — verify, commit remaining work with the emoji-:: convention, push, and open a PR to develop that passes the PR title check CI. Use when the user says "PR 올려", "출고", "ship", "머지 준비".

ship

Take the current branch from "code done" to "PR open" following repo conventions.

Steps

Identify the issue number from the branch name ({type}/{N}-{slug}). If it doesn't contain one, ask the user — the PR title check CI requires (#N).
Verify first: run the verify-loop skill. Do not push failing code.
Commit any remaining changes in Korean, one logical change per commit:
```
{emoji} :: {한국어 요약}
```
Emoji: ✨ feature · ♻️ refactor · 💄 UI/style · 🎨 format · 🐛 bugfix · 🔧 config/CI. Never commit .env.dev/.env.prod or generated *.g.dart/*.freezed.dart files.
Push: git push -u origin {branch}.
Open the PR against develop:
- Title (must match CI regex ^[^ ] :: \(#[0-9]+\) - .+): 🔀 :: (#{N}) - {한국어 제목} Before creating, propose ~3 candidate {한국어 제목} options via AskUserQuestion and let the user pick (or edit) — don't auto-name. The 🔀 :: (#{N}) - prefix is fixed; only the Korean title varies.
- Body: fill .github/PULL_REQUEST_TEMPLATE.md in Korean — 개요, Closes #{N}, 작업내용 (bulleted actual changes), 테스트 방법 (concrete steps), 스크린샷 (placeholder note if UI changed but no screenshot available), 질문사항, 체크리스트 (check only what was actually verified).
- Korean body encoding (Windows/PowerShell): never pipe a here-string into gh ... --body-file - — PowerShell 5.1 encodes native-command stdin in the system codepage and mangles Hangul into ?. Write the body to a UTF-8 file first, then pass its path:
```
gh pr create --base develop --title "🔀 :: (#{N}) - {제목}" --body-file pr_body.md
```
  (Same for gh pr edit --body-file and gh issue create/edit --body-file.) Use the Write tool to create the file (it writes UTF-8), then delete it after. The PR title via --title "..." is fine inline.
Update the issue label to 🌟 Status: Reviewing.
Report the PR URL and the verification results.

Constraints

Base branch is always develop (never main).
Don't merge the PR or enable auto-merge — review is human-gated.
If the branch is behind develop, merge develop in and re-verify before pushing.