git/skills/pr/SKILL.md

name, description

name

description

pr

Commit all changes via jsc-git:commit, create a target branch named from the highest-priority commit type plus a summarized title, push, then open a Gitea PR with the templated description against the base branch the caller passed in (falling back to develop, main, master only when none was given). Branch priority is revert > fix > feat > perf > refactor > test > docs > style > chore. Use when work is ready for review; not for plain commits.

pr — create a Push Request

Steps

1. Call jsc-git:commit to commit every file change first. Done when git status --porcelain prints nothing.
2. Resolve the base branch: tools/base-branch.sh {base branch the caller passed in, omitted when the caller passed none}. A base branch passed in by the caller wins over everything else — jsc-sdlc:implement passes the analysis page's source branch, and silently retargeting that PR at develop would merge a single work package straight past the feature branch it belongs to. Done when the script prints one branch name; a non-zero exit → report and stop, never fall back silently.
3. Create the target branch from the remote base branch:
   1. Take the type with the highest priority across all commits: revert > fix > feat > perf > refactor > test > docs > style > chore. Done when exactly one type is picked.
   2. Summarize one title from all commit messages. Done when one title line covers every commit in the range.
   3. Translate the requirement and the title into a short English phrase, then run tools/slugify.sh {type} {phrase} to build the target branch name {type}/{requirement or feature}-{title} (example: a non-English request to export order reports becomes the phrase order export report, then feat/order-export-report). Done when the script prints one slug on stdout; exit 2 (non-ASCII input) or exit 3 (empty slug) → re-translate the title into an English phrase and retry, never hand-build the branch name.
   4. Run git checkout -b {target branch} origin/{base branch} so the branch starts at the remote base, then bring step 1's commits onto it (git cherry-pick them when they landed on another branch). Done when git branch --show-current prints the target branch and git log --oneline origin/{base branch}..HEAD lists exactly step 1's commits.
4. Run git push -u origin {target branch}. Done when git ls-remote --heads origin shows the target branch's ref.
5. Create the PR: jsc-gitea/tools/gitea.sh pr-create {owner}/{repo} {target branch} {base branch} "{branch name}" {description file}.
   • Title = branch name.
   • Write the description into a temp file first, using templates/pr-description.md (a Traditional Chinese template; the generated description stays in Traditional Chinese per the STE100 output rule).
   • Done when the command prints a PR URL; no URL → report the error and stop.
6. Prerequisite PR blocking: when the description lists a prerequisite Push Request, run jsc-gitea/tools/gitea.sh pr-depend {owner}/{repo} {this PR number} {prerequisite owner}/{repo} {prerequisite PR number} to add the dependency. Gitea then blocks merging until the prerequisite PR closes. On exit 4 (the dependency API call failed) degrade: prefix the PR title with WIP:, which Gitea blocks merging on natively, and record in the PR description that the prefix comes off once the prerequisite PR closes. Done when pr-depend printed OK {owner}/{repo}#{number} depends on ..., or the PR title starts with WIP: and the description names the prerequisite PR.
7. Report the PR URL. Done when the reported URL is the one step 5 printed, together with the base branch and the target branch it was opened against.

Rules

1. No template section may stay empty: fill the literal 「無」 when there is no plan page, analyze page, or prerequisite PR.
2. Read the jsc-sdlc plan page and analyze page through jsc-gitea:wiki, which resolves JSC_WIKI_REPO_PLAN for the plan page and JSC_WIKI_REPO_ANALYZE for the analyze page from the inherited environment, falls back to JSC_WIKI_REPO, and asks only when neither is set. Each page type reads its own variable only; a page type never borrows another type's variable. Take both links from the pages read this way; the analyze link must point at the work package heading anchor.
3. Branch title summarization (step 3.2) and description drafting MUST run as a sub agent.