AGENT SKILL

ywc-create-pr

(ywc) Use when the user wants to open a pull request and says "create a PR", "open a PR", "submit code for review", "push and create PR", "PR 만들어줘", "풀리퀘 작성", "プルリク作成", or is wrapping up a feature branch. Do not use for committing only without PR creation, or for handling existing PR review comments (use ywc-handle-pr-reviews).

License 许可
MIT
最近更新
2026-11-08
Stars
★ 8
Forks
1

01 前言 Front Matter

name
ywc-create-pr
description
(ywc) Use when the user wants to open a pull request and says "create a PR", "open a PR", "submit code for review", "push and create PR", "PR 만들어줘", "풀리퀘 작성", "プルリク作成", or is wrapping up a feature branch. Do not use for committing only without PR creation, or for handling existing PR review comments (use ywc-handle-pr-reviews).

02 资源文件 12

03 SKILL.md 正文

Create PR

Announce at start: "I'm using the ywc-create-pr skill to commit and open a pull request."

Commit changes and create a draft PR following the PR template.

Rationalization Defense

When tempted to skip a step, check this table first:

Excuse Reality
"User said 'create PR' — they obviously want it merged too" Default is draft PR. Mark ready/merge only when explicitly asked.
"CI check is slow, just push and let CI run remotely" Local CI catches failures before review delay. Skip only with --skip-ci-check.
"Force push will resolve the rejection faster" Non-fast-forward = teammate work or rebase needed. Force only with explicit user approval.
"The PR template is generic, my custom body is better" If .github/pull_request_template.md exists, follow it. Templates encode team norms.
"Secret scan flagged a value but it's just a test fixture" Stop and confirm with the user before bypassing the scan. Better to over-confirm than leak.
"Base branch is obvious from history" Auto-detect order is develop → main → master. Show the chosen base before proceeding.
"The hook is just being pedantic, CLAUDE_MD_CHECK=skip git push will fix it" Inline VAR=value git push does NOT reach the hook subprocess — the hook runs before the command executes. Use export VAR=value && git push in a single Bash call instead, or instruct the user to run ! VAR=value git push in their terminal.
"CI passed locally, so remote CI will pass too" Remote CI may use different OS runners, Node versions, or environment secrets unavailable locally. Always verify remote CI after pushing — local and remote diverge more often than expected.
"CI is slow — let the reviewer catch failures" CI failures signal a broken branch to every reviewer. Fix them immediately after PR creation so the PR stays reviewable and avoids a second round-trip after the reviewer waits for another push.
"CI is green, so the PR is ready to merge" CI status and merge-readiness are independent gates. A green PR can still be CONFLICTING against the base if the base advanced. Check gh pr view --json mergeable,mergeStateStatus before declaring the PR done — a CONFLICTING/BEHIND/BLOCKED PR blocks every reviewer just like a CI failure.
"The PR conflicts with base — I'll rebase the feature branch to fix it" Rebasing rewrites commit SHAs and orphans existing PR review threads. Merge the base into the feature branch instead (git merge --no-ff origin/<base>); it preserves SHAs and review history. See ../references/pr-conflict-resolution.md.
"The UL update adds noise before every PR" The update is a diff-driven incremental review, not a full re-extraction. If no new domain terms appeared in the branch, the skill produces no changes. Skipping it lets the glossary drift from the codebase with every PR that introduces new vocabulary.
"Security scan and CI already checked the branch, so I do not need to read the diff" Automated checks do not catch scope creep, drive-by edits, debug residue, or convention mismatch. Before PR creation, the author must read git diff <base-branch>...HEAD; this does not replace independent reviewer or CI review.
"Checking the task README too is extra work, just fuzzy-match the plan folder" The task README's ## Spec Reference → Primary Sources is already recorded precisely by ywc-task-generator — it is the authoritative source. Path A (task lookup) always runs before Path B (fuzzy match), never the reverse.
"Completed plans always live in OLD/, so I only need to search that folder" The subdirectory name for completed plans is project-specific (OLD, archive, done, etc.). Search docs/ywc-plans/**/*.md recursively instead of hardcoding one folder name.
"docs/ywc-plans/ is missing, treat it as an error" Other projects reusing this skill may never have created the directory, or it may be .gitignored. Absence is a normal state — skip Step 6.6's Path B silently, never surface it as a failure.

Violating the letter of these rules is violating the spirit. If you find yourself rephrasing a rule to make an exception, stop and ask the user.

Context

  • Changed files: !git status --short
  • Current branch: !git branch --show-current

Task

Follow the steps below to commit and create a PR.

0. Language and Title Initialization

  1. Title: Check $ARGUMENTS for --title "<value>". If present, store it as the PR title — it will be used verbatim in Step 7 (skip self-generated title).
  2. Language: Check $ARGUMENTS for a language hint. First-class PR languages are en (English), ja (Japanese), ko (Korean), zh (Simplified Chinese), and es (Spanish). Accept code and name hints such as --lang ja, --lang en, --lang zh, --lang es, --language korean, --language chinese, and --language spanish. If not specified, resolve PR prose language using ../references/language-resolution.md: project .codex/ywc.json, project guidance (AGENTS.md, CODEX.md, CLAUDE.md), user ~/.codex/ywc.json, then ask. If --title was provided, keep that title verbatim; the resolved language controls generated PR body prose and any generated title only.
  3. Apply the chosen language consistently when writing the PR description in Step 7. Localize only PR title/body prose; keep branch names, task IDs, file paths, commands, labels, code blocks, YAML keys, JSON keys, and other machine identifiers unchanged.
  4. Post-CI check: Check $ARGUMENTS for --skip-post-ci-check. If present, skip Step 8 (Remote CI & Bot Review). This flag is passed by ywc-finish-branch, which handles CI verification independently in its own Step 4.
  5. Ubiquitous Language update: Check $ARGUMENTS for --skip-ubiquitous-update. Store the flag — it controls Step 0.5.
  6. Plan-doc override: Check $ARGUMENTS for --plan-doc <path>. If present, store the path — Step 6.6 treats it as the single confident candidate and skips its own Task/Plan discovery (Path A/B).
  7. Plan-doc opt-out: Check $ARGUMENTS for --no-plan-ref. Store the flag — it disables Step 6.6 entirely. Mutually exclusive with --plan-doc; if both are present, --plan-doc wins and --no-plan-ref is ignored.

0.5. Ubiquitous Language Update (optional)

Skip this step if --skip-ubiquitous-update is present in $ARGUMENTS. This flag is passed by ywc-finish-branch, which runs the update in its own Step 1.5 before delegating PR creation to this skill.

Check whether docs/ubiquitous-language.md exists in the project root:

test -f docs/ubiquitous-language.md
  • Exists: Invoke ywc-ubiquitous-language --mode update. Any changes to docs/ubiquitous-language.md will be picked up and committed by Step 4.
  • Not exists: Skip silently — the project has not yet established a ubiquitous language document.

1. Determine Base Branch

  • If a base branch is specified in $ARGUMENTS, use it
  • Otherwise, auto-detect the default base branch in the following priority order:
    1. develop — if it exists locally or in remote (git rev-parse --verify develop 2>/dev/null || git rev-parse --verify origin/develop 2>/dev/null)
    2. main — if it exists locally or in remote
    3. master — fallback
  • Store the determined base branch and use it consistently throughout all subsequent steps
  • Show the determined base branch to the user: "Base branch: <branch>"

2. Pre-flight Checks

Before proceeding, verify the environment is ready:

  • Confirm gh CLI is installed and authenticated (gh auth status). If not, stop and tell the user how to set it up
  • Check if a PR already exists for this branch (gh pr list --head <current-branch> --state open). If one exists, show the URL and ask the user whether to update it or create a new one
    • If update: Skip PR creation (Step 7), but do not skip Step 8. Commit and push changes, optionally update the PR description with gh pr edit <number> --body-file -, then proceed to Step 8 (Remote CI & Bot Review Check). Updating a PR can break CI exactly like creating one — the verification must run on the update path too, not only on the new-PR path (unless --skip-post-ci-check was passed by an upstream caller).
    • If new: Continue with the full workflow
  • Verify the current branch is not the base branch itself — refuse to create a PR from main/develop/master to itself

3. Security Check

Run the bundled secret scan script:

# Phase 1+2: dangerous file names + staged/unstaged diff and untracked file content
RESOLVER_LAUNCHER="$(bash "${CODEX_HOME:-$HOME/.codex}/skills/scripts/select-resolver-launcher.sh" 2>&1)" || { echo "BLOCKED: ${RESOLVER_LAUNCHER#BLOCKED: }" >&2; exit 3; }
# A resolver failure must never exit 1, which reads as "secrets found": stop as BLOCKED.
SECRET_SCRIPT="$(bash "$RESOLVER_LAUNCHER" "ywc-create-pr/scripts/scan-secrets.sh" bash)" || { echo "BLOCKED: resolver failed ($?)" >&2; exit 3; }
bash "$SECRET_SCRIPT" --staged

# Phase 3: all commits on this branch vs base (secrets and dangerous file names already committed)
bash "$SECRET_SCRIPT" --committed <base-branch>

Exit 0 = clean — proceed. Exit 1 = secrets or dangerous files found — the script prints the matching lines to stdout with each matched value shown as [REDACTED]. Any other result (exit 2 = usage error, not a git work tree, an invalid or unresolvable --committed base, or a failed scan step — a git call, mktemp, reading an untracked file, or the added-line filter; exit 3 = the resolver BLOCKED; or any other code) means nothing was scanned: treat it as BLOCKED and stop — never as clean.

If either scan returns exit 1, warn the user and show the script output. Do not include flagged files in the commit unless the user explicitly confirms. For committed secrets (second scan), require explicit confirmation before proceeding to PR creation.

4. Commit Uncommitted Changes

  • Check uncommitted changes with git status and git diff
  • If there are uncommitted changes, delegate to ywc-commit with --skip-ubiquitous-update:
    • Why the flag: Step 0.5 of this skill already invoked ywc-ubiquitous-language --mode update (unless this skill itself was called with --skip-ubiquitous-update by an upstream caller like ywc-finish-branch). Without the flag, ywc-commit's own Step 0.5 would run the update a second time. The flag must always be passed in this delegation — even when this skill's Step 0.5 was skipped, because the upstream caller is the one responsible for the UL update in that scenario.
    • ywc-commit classifies every changed file as IN / UNKNOWN / OUT relative to the current session, splits logically distinct changes into separate commits, and learns the project's commit message style from git log
    • It will confirm with the user before staging any UNKNOWN or OUT files — do not skip that confirmation
    • Follow the repository's observed co-author trailer convention; do not force-add a trailer if the repository does not already use one
  • If there are no uncommitted changes: skip this step

5. CI Check (Pre-push Validation)

Run the same lint, format, typecheck, and test checks locally that CI will execute. The goal is to catch failures before pushing, since CI failures delay PR review.

Skip this step if --skip-ci-check is present in $ARGUMENTS.

5-1. Detect CI Check Commands

Run the bundled detector first — it emits candidate commands from each source plus the package manager, so you do not re-derive the same greps each run:

RESOLVER_LAUNCHER="$(bash "${CODEX_HOME:-$HOME/.codex}/skills/scripts/select-resolver-launcher.sh" 2>&1)" || { echo "BLOCKED: ${RESOLVER_LAUNCHER#BLOCKED: }" >&2; exit 3; }
CI_DETECT_SCRIPT="$(bash "$RESOLVER_LAUNCHER" "ywc-create-pr/scripts/detect-ci-commands.sh" bash)" || exit $?
bash "$CI_DETECT_SCRIPT" [repo-dir]

It is best-effort; reconcile its output against the priority order below (workflows are authoritative, then CLAUDE.md, then package.json, then Makefile):

  1. .github/workflows/*.yml — Read CI workflow files and extract active check commands
    • Look for run: fields containing lint, format, typecheck, type-check, test, check
    • Exclude deployment-related jobs/steps (deploy, release, publish, docker build)
    • Prioritize workflows with on: pull_request or on: push triggers
  2. CLAUDE.md — Search the project root CLAUDE.md (or parent directory) for lint, format, typecheck, and test commands
  3. package.json scripts — Use scripts whose keys match lint, format, typecheck, type-check, or test
  4. Makefile — Use targets named lint, format, check, or test

If no commands are detected, skip this step and inform the user of the reason.

5-2. Detect Execution Environment

  • If CLAUDE.md specifies a docker exec <container> prefix, apply it to all commands
  • Determine the package manager (pnpm, npm, yarn, etc.) from the lock file

5-3. Run Checks

  • Execute all detected check commands in sequence (recommended order: lint → format → typecheck → test)
  • Record the pass/fail result of each command
  • Continue running remaining commands even if one fails — report all results together at the end

5-4. Report Results and Next Steps

  • If all checks pass, proceed to the next step (Push)
  • If any check fails:
    • Summarize which checks failed and what the errors were
    • Present the user with two options:
      1. Fix and retry — Resolve the issues, then re-commit and re-run checks
      2. Skip and proceed — Ignore the check failures and continue to Push & PR creation

6. Push to Remote

  • Check if the current branch is already up-to-date with the remote (git status -sb — look for ahead count). If the branch is already pushed and there are no new local commits, skip the push
  • Push to remote with git push -u origin HEAD
  • If push fails due to a PreToolUse hook error (error message contains "hook error" or "Blocked:"):
    1. Read the full hook error message — it usually states exactly what is required or how to bypass
    2. Look for a bypass env var hint (e.g., CLAUDE_MD_CHECK=skip, SKIP_CHECK=true). If found:
      • Retry with export <BYPASS_VAR>=<value> && git push -u origin HEAD in a single Bash call
      • Why: VAR=value git push sets the variable only for the git process, not for the hook subprocess that runs before it. Exporting in the same shell command makes the variable available to the hook
    3. If the hook requires a content action (e.g., "update CLAUDE.md before pushing"):
      • Evaluate whether the requirement genuinely applies to the changed files
      • If yes: fulfill the requirement (e.g., update CLAUDE.md), then retry the push normally
      • If no (e.g., changes are test fixtures or QA docs with no documentation impact): use the bypass approach in step 2
    4. If the bypass attempt also fails or no bypass is indicated, instruct the user to run this in their terminal:
      ! export <BYPASS_VAR>=<value> && git push origin HEAD
      
      Explain: the ! prefix runs the command directly in the user's shell session, where the exported variable reaches the hook subprocess. Continue to Step 7 once the user confirms the push succeeded
  • If push fails due to remote changes (non-fast-forward):
    • Suggest git pull --rebase origin <current-branch> to the user (rebase against the same feature branch, not the base branch)
    • Do not force-push without explicit user approval

6.5. Author Self-Review Gate

Before creating or updating the PR, perform an explicit author diff review:

git diff <base-branch>...HEAD

Read the full diff and reject the branch for cleanup before PR creation if any of the following appear:

  • Scope creep outside the stated task or PR purpose
  • Debug residue, temporary logging, commented-out experiments, or local-only notes
  • Drive-by edits unrelated to the branch goal
  • Secrets, credentials, tokens, internal URLs, or sensitive local paths
  • Convention mismatch against AGENTS.md, CODEX.md, CLAUDE.md, existing file style, or the PR template

Record the result in the PR description as Author Self-Review Gate: passed. This gate does not replace independent reviewer, CI, secret-scan, or bot-review checks; it only ensures the author has read the complete branch diff before asking others to review it.

6.6. Discover Related Task/Plan/Design-Intent Document (best-effort, non-blocking)

Skip this step entirely if --no-plan-ref is present in $ARGUMENTS and --plan-doc is absent. If both flags are present, --plan-doc takes precedence and proceeds to sub-step 1.

PR bodies generated purely from diff/commit history lose the why behind a design decision already captured by ywc-brainstorm/ywc-plan in docs/ywc-plans/ or by ywc-task-generator in a task README's ## Spec Reference. This step looks for that document and, when found with confidence, holds it for Step 7 to cite in a design-background section. It never blocks PR creation — no match is a normal, silent outcome.

  1. Explicit override. If --plan-doc <path> is present, validate it first: the path must be repository-relative (reject a leading / or any .. segment) and must end in .md. String checks alone do not stop a symlink from pointing outside the repository, so also resolve the candidate to its canonical path (realpath <path>) and reject it unless the result is still inside the repository root (git rev-parse --show-toplevel). Read that canonical path from here on, never the original argument — re-resolving the original leaves a window in which the symlink is repointed between the check and the read. If invalid, missing, or unreadable, print one line explaining why and continue to Step 7 with no design-background result; do not fall back to Path A/Path B. If valid and readable, treat it as the single confident candidate and continue to sub-step 6.
  2. Path A — Task-based lookup (authoritative, tried first).
    • If the current branch does not start with feature/, Path A has no candidate; go to Path B.
    • Let <task-name> be the branch name with feature/ stripped. Glob tasks/<task-name>/README.md; if absent, Glob tasks/completed/<task-name>/README.md.
    • If neither exists, Path A has no candidate; go to Path B.
    • If found, read the file and extract its ## Spec Reference section: the ### Primary Sources list and ### Summary text. If Primary Sources says N/A — no external spec (housekeeping / refactor / config only) (or equivalent), treat Path A as having no candidate and go to Path B.
    • Otherwise hold {source: "task", task_readme_path, primary_sources, summary} as the confident result and skip Path B.
  3. Path B — Plan-directory fuzzy match (fallback, only when Path A found no candidate).
    • Glob docs/ywc-plans/**/*.md recursively. Exclude *.spec-ready-log.md and */architecture-verdict.md sidecar files.
    • If docs/ywc-plans/ does not exist or the Glob returns zero files, stop silently. Use filesystem Glob/Read only — never git log/git ls-files, since the directory may be untracked or ignored.
  4. Branch-to-filename token match (Path B only).
    • Strip one leading <type>/ segment (feature/, fix/, chore/, etc.), tokenize the remainder on -/_/. into lowercase tokens, and drop tokens shorter than 4 characters to avoid false matches from the recurring ywc prefix.
    • For each candidate basename, strip its YYYYMMDD- prefix, optional small_ prefix, and .md suffix, then tokenize the same way; ignore the candidate's directory.
    • A candidate is confident when it shares at least 2 tokens, or exactly 1 token of at least 6 characters.
  5. Resolve Path B matches. Zero matches stop silently. One match holds {source: "plan", plan_path}. Two or more matches must not be guessed: print one line listing the candidates and instruct the user to rerun with --plan-doc <path>, then continue to Step 7 without a design-background result.
  6. Excerpt extraction (source: "plan" or override only). Bound the read before it happens — a large plan file would otherwise burn the context this PR still needs. Bound it on bytes, not lines — a 120-line cap still admits a single multi-megabyte line. Take the excerpt source from head -c 8192 <plan_path> (first 8 KB, truncated mid-line if needed), never a full-file read. Within that window, take the content under ## Goal or ## Purpose until the next ## heading, capped at 5 lines / approximately 500 characters. If neither heading exists, use the first paragraph after the title with the same cap. Never forward the full file. Also look, within that same bounded window, for a ## Alternatives Considered or ## Trade-offs heading (whichever appears first), take the content under that heading until the next ## heading, and apply the same 5-line / ~500-character cap — this is opportunistic: no current plan template guarantees the section exists, so its absence is the normal case and produces no finding, not a gap to fill by inventing content. Hold {source: "plan", plan_path, excerpt, alternatives_excerpt?, alternatives_heading_kind?} — alternatives_excerpt and alternatives_heading_kind ("alternatives" or "trade-offs", recording which of the two source headings was actually found) are present only when that heading was found. Step 7 uses alternatives_heading_kind to pick the matching localized sub-heading — never hardcode "Alternatives Considered" regardless of which heading the source file used.
  7. Untracked-source confirmation gate. Whatever the source, if git does not track the document (git ls-files --error-unmatch <path> exits non-zero — the normal case for a .gitignored docs/ywc-plans/), its text has never passed review and may hold local secrets or PII that this step would publish verbatim to a remote PR. Show the user the path and the exact excerpt, and ask for explicit confirmation before citing it. On decline, continue to Step 7 with no design-background result. Tracked documents skip this gate.
  8. Hold {source: "task", ...}, {source: "plan", ...}, or nothing for Step 7. This step performs no writes.

7. Create PR

  • Check if .github/pull_request_template.md exists

    • If exists: Read the template and create the PR description following its structure

    • If not exists: Create a PR description with the following default structure:

      ## Summary
      
      [1-3 bullet points summarizing the changes]
      
      ## Changes
      
      [Feature list: what / where / why per item — see references/pr-body-features-api.md]
      
      ## Test Plan
      
      [How to verify the changes]
      
  • Write each section based on all commits from the base branch (git log <base-branch>..HEAD)

  • Use the full diff already read in Step 6.5 to ensure the description accurately reflects the changes — do not fetch it again

  • Feature list and API table: write Changes as features (what / where / why, supported by evidence). Include a Method+Path API table only for endpoint additions/deletions or route-bound request/response/auth/status contract changes; omit it for internal refactors.

    Action required: Read references/pr-body-features-api.md for evidence rules, localized labels, and placement. On the existing-PR update path, Step 7 and this reference remain skipped.

  • Impact (optional) — For observable behavior changes only, write a concise localized block with affected scope and concrete Before/After behavior. Reuse the diff already read during author review; anchor claims to that evidence and omit unsupported outcomes. Omit Impact for docs-only changes or when no observable behavior changes. Localize heading/labels/prose to Step 0's resolved language; respect the repository PR template by using its matching section or fitting the block within its existing structure. Do not replace/reorder required template sections. Do not add another diff acquisition or a collection phase solely for Impact. No screenshot operations or publishing-authority changes.

  • PR title: if --title was provided in Step 0, use it verbatim. Otherwise, generate a title from the commit history in the language resolved in Step 0 (en, ja, ko, zh, or es).

  • Write all description prose in the language chosen in Step 0. Do not translate branch names, task IDs, file paths, commands, labels, code blocks, YAML keys, JSON keys, or other machine identifiers.

  • If there are no UI changes, write "N/A" in the screenshot section (if the template has one)

  • Design Background (optional, appended): if Step 6.6 held a result, append this section after the template/default body above. This augments the body; it never replaces or reorders the project's template structure. Localize the heading and intro line to the language chosen in Step 0; keep the quoted summary/excerpt verbatim:

    Language Heading Intro (source: "task") Intro (source: "plan")
    en ## Design Background > Derived from task \<task_readme_path>`'s Spec Reference.` > Excerpted from \<plan_path>` — see the file for full context.`
    ko ## 설계 배경 (Design Background) > task \<task_readme_path>`의 Spec Reference에서 도출됨.` > \<plan_path>`에서 발췌 — 전체 맥락은 원문 참조.`
    ja ## 設計背景 (Design Background) > タスク \<task_readme_path>` の Spec Reference から抽出。` > \<plan_path>` から抜粋 — 全文は原文参照。`
    zh ## 设计背景 (Design Background) > 源自任务 \<task_readme_path>` 的 Spec Reference。` > 摘自 \<plan_path>` — 完整内容请参见原文件。`
    es ## Antecedentes de diseño (Design Background) > Derivado de la Spec Reference de la tarea \<task_readme_path>`.` > Extraído de \<plan_path>` — consulte el archivo para el contexto completo.`

    Alternatives Considered / Trade-offs (optional, source: "plan" only): if Step 6.6 held an alternatives_excerpt, append one further sub-block after the excerpt above, using the localized sub-heading that matches alternatives_heading_kind — pick the "alternatives" column when the source file's heading was ## Alternatives Considered, or the "trade-offs" column when it was ## Trade-offs. Never default to the "alternatives" column when alternatives_heading_kind is "trade-offs" — the label must match what the source document actually said. Omit the whole sub-block entirely when alternatives_excerpt is absent — most plan documents will not have one, and that is the normal case, not a gap:

    Language Sub-heading (alternatives_heading_kind: "alternatives") Sub-heading (alternatives_heading_kind: "trade-offs")
    en ### Alternatives Considered ### Trade-offs
    ko ### 검토했던 대안 (Alternatives Considered) ### 트레이드오프 (Trade-offs)
    ja ### 検討した代替案 (Alternatives Considered) ### トレードオフ (Trade-offs)
    zh ### 已考虑的替代方案 (Alternatives Considered) ### 权衡取舍 (Trade-offs)
    es ### Alternativas consideradas (Alternatives Considered) ### Compensaciones (Trade-offs)
    <localized sub-heading matching alternatives_heading_kind>
    
    <alternatives_excerpt text, verbatim>
    

    For source: "task", include the localized heading, intro, **Primary Sources**: <primary_sources>, and the verbatim summary. For source: "plan" (including --plan-doc), include the localized heading, intro, and verbatim excerpt. The quoted summary/excerpt/alternatives_excerpt text itself stays verbatim (it is a quotation, not translated). If Step 6.6 held no result, omit the section entirely — never add an empty placeholder.

  • Write the finished body to a temp file and create a draft PR with gh pr create --draft --base <base-branch> --title "<title>" --body-file "$body_file". Do not pipe the body through a <<'EOF' heredoc: the Design Background block carries verbatim third-party document text, and a line reading exactly EOF inside it would close the heredoc early and hand the remainder to the shell as commands.

  • Always specify --title and --body-file explicitly to avoid interactive prompts

8. Remote CI & Bot Review Check

Skip this step entirely if --skip-post-ci-check is present in $ARGUMENTS. This step runs only when ywc-create-pr is invoked directly by the user — ywc-finish-branch passes --skip-post-ci-check and handles CI + bot review in its own Step 4.

After the PR is created or updated (the Step 2 update path also lands here), retrieve the PR number and verify that remote CI passes and no automated reviewers have flagged issues.

PR_NUMBER=$(gh pr view --json number --jq .number)

8-1. Wait for CI to Complete

gh pr checks $PR_NUMBER --watch
# exit 0 = all checks passed; exit 1 = one or more checks failed

If no CI checks are configured for this repository (command returns immediately with no output), skip to Step 8-3. If --skip-ci-check is present in $ARGUMENTS, skip to Step 8-3.

8-2. CI Failure Fix Loop (up to 2 attempts)

If gh pr checks exits 1, at least one check failed. Apply fixes in the loop below — at most 2 attempts:

  1. Get failure details:

    # List failed run IDs for the current branch
    gh run list --branch $(git branch --show-current) \
      --json databaseId,name,conclusion \
      --jq '.[] | select(.conclusion == "failure")'
    # View logs for the most recent failed run
    gh run view <run-id> --log-failed
    
  2. Categorize and fix by failure type:

    Failure type Fix action
    Lint / format Run the project's auto-fix command (eslint --fix, prettier --write, ruff --fix, biome check --apply), commit the changes
    Type errors Read compiler output, fix type mismatches in affected files, commit
    Test failures Analyze failing test output, fix the implementation (never disable or weaken tests), commit
    Build errors Read compiler/bundler output, fix compilation or import errors, commit
  3. Push the fixes and re-run gh pr checks $PR_NUMBER --watch to re-verify.

  4. After 2 failed fix attempts, report the failing check name(s) with the last 30 log lines, leave the PR as draft for manual intervention, and note the CI failure in the Completion Report.

8-3. Bot Review Polling

Action required: Read codex/skills/references/pr-bot-polling.md before proceeding. The canonical polling procedure and parameters are defined there.

bash "${CODEX_HOME:-$HOME/.codex}/skills/scripts/poll-pr-reviews.sh" "$PR_NUMBER"
# exit 0 → BOT_COUNT > 0 (bot reviews posted)
# exit 1 → BOT_COUNT == 0 (no bot reviews within polling window)

# Required before claiming the PR is ready: proves the poll completed.
bash "${CODEX_HOME:-$HOME/.codex}/skills/scripts/poll-pr-reviews.sh" --verify "$PR_NUMBER"

Allow the polling command at least 600 seconds. If it or --verify fails, report the PR as BLOCKED/DONE_WITH_CONCERNS; never convert that result to zero bot comments or claim the PR is ready. Invoke ywc-handle-pr-reviews as a PR health sweep regardless of BOT_COUNT == 0. A zero bot-comment count is not terminal success; the handler still checks review artifacts, CI status, and merge-readiness. If the handler applies fixes, re-run gh pr checks $PR_NUMBER --watch, then re-run the polling script, --verify, and health sweep until no new review artifacts, CI failures, or merge-readiness blockers remain, or until the handler reports a non-recoverable blocker.

8-4. Merge-Readiness (Conflict) Check

Action required: Read ../references/pr-conflict-resolution.md before proceeding. The mergeable / mergeStateStatus semantics, the merge-not-rebase rule, and the surface-vs-auto-resolve boundary are defined there.

CI passing does not mean the PR is mergeable — the base branch may have advanced and now conflict. After CI and bot review settle, check the merge state:

gh pr view $PR_NUMBER --json mergeable,mergeStateStatus --jq '{mergeable, mergeStateStatus}'
  • MERGEABLE / CLEAN → the PR is review-ready; proceed to Completion Report.
  • BEHIND → the branch is merely out of date (no textual conflict). Follow Update Branch From Base for the fast catch-up, push, and re-verify CI.
  • CONFLICTING / DIRTY → follow Update Branch From Base in the reference. If the merge auto-resolves (branch was merely behind), push and re-verify CI. If it reports real textual conflicts, surface the conflicting files and PR URL to the user and note the conflict in the Completion Report — do not auto-resolve or force-push.
  • BLOCKED → a required check or review gate is missing — not a conflict. Do not run the base-merge procedure; report which required check or review is outstanding so it can be resolved.
  • UNKNOWN → poll briefly per the reference, then re-read.

Because this skill creates a draft PR by default and does not merge, a conflicting result is reported (not a hard stop) unless the user asked to take the PR further — but the branch should still be brought up to date so reviewers see a mergeable PR.

9. Completion Report

Display:

  • The created PR URL (clickable)
  • Summary: number of commits, files changed, insertions/deletions
  • Base branch used

Notes

  • Follow any additional instructions in $ARGUMENTS
  • Never force-push or amend published commits without explicit user approval
  • If any step fails, explain what went wrong and suggest the fix rather than silently retrying

Integration

  • upstream: Direct user request, or ywc-finish-branch when it needs PR creation/update as part of branch delivery.
  • internal delegation: ywc-commit for explicit staging/commit discipline; ywc-ubiquitous-language for glossary drift checks unless an upstream caller already handled it.
  • downstream: ywc-handle-pr-reviews for review-comment resolution after PR creation; ywc-finish-branch for mark-ready, merge, and post-merge cleanup.
  • out of scope: Merging PRs, resolving review comments, and broad implementation review. Those remain owned by ywc-finish-branch, ywc-handle-pr-reviews, and ywc-impl-review.

Output Format

Return a PR creation report:

Status: <DONE | DONE_WITH_CONCERNS | BLOCKED | NEEDS_CONTEXT>
PR: <URL or "not created">
Base branch: <detected or requested base>
Commits: <commits created or "already committed">
Validation: <local checks, sensitive-file scan, and CI/bot status>
Next action: <merge/review instruction or blocker>

Validation

Before finalizing, verify that sensitive files were not committed without confirmation, staged files were explicit, base branch selection is reported, gh authentication was checked, and CI or bot-review handling follows the selected mode.

04 同仓库更多 Skills

yongwoon
yongwoon/ywc-agent-toolkit

missing-frontmatter

暂无简介

★ 8
yongwoon
yongwoon/ywc-agent-toolkit

malformed-frontmatter

暂无简介

★ 8
yongwoon
yongwoon/ywc-agent-toolkit

fixture-501-fail

(ywc) Use when aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa Do not use for x.

★ 8
yongwoon
yongwoon/ywc-agent-toolkit

fixture-500-pass

(ywc) Use when aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa Do not use for x.

★ 8
yongwoon
yongwoon/ywc-agent-toolkit

ywc-worktrees

(ywc) Use when creating, auditing, pruning, or resolving git worktrees for isolated task workspaces, whether delegated from an executor or used standalone. Triggers: "worktree 생성", "worktree audit", "worktree 정리", "worktree prune", "ywc-worktrees", "create worktree". Do not use for branch creation/deletion alone, PR creation (use ywc-create-pr), CI or merge delivery (use ywc-finish-branch), task orchestration (use ywc-sequential-executor or ywc-parallel-executor), or non-git isolation.

★ 8
yongwoon
yongwoon/ywc-agent-toolkit

ywc-wayfinder

(ywc) Use when a large or uncertain change needs multi-session discovery with a deterministic local map and exactly one active ticket before planning or implementation. Triggers: "wayfinder", "길찾기", "discovery map", "multi-session discovery", "탐색 ticket", "経路整理", "探索マップ", "ywc-wayfinder". Do not use for ordinary planning (use ywc-plan), idea clarification (use ywc-brainstorm), direct implementation, or tracker/database writes outside the local Markdown map.

★ 8