[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72TJ1TCT511CVS5YR90HDV7":3,"skill-same:01M72TJ1TCT511CVS5YR90HDV7":97},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M72TJ1TCT511CVS5YR90HDV7","ywc-handle-pr-reviews",null,"(ywc) Use when an open GitHub PR has review threads, comments, or feedback that must be fetched, fixed, replied to, marked, pushed, and CI-verified. Triggers: \"handle PR reviews\", \"review comments\", \"리뷰 대응\", \"レビュー対応\", \"ywc-handle-pr-reviews\". Do not use for standalone feedback before PR automation (use ywc-receive-review), new PR creation (use ywc-create-pr), doing the code review yourself (use ywc-impl-review), review learnings (use ywc-review-learnings), or changes outside open-PR context.","yongwoon\u002Fywc-agent-toolkit","yongwoon","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9317029?v=4","01M72SZSF6VKANKG5QTMV4V95S","01M72SZSG8HHC3W2CV5P7EJ5AH",8,"MIT","https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fywc-agent-toolkit\u002Fskills\u002Fywc-handle-pr-reviews\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: ywc-handle-pr-reviews\ndescription: >-\n  (ywc) Use when an open GitHub PR has review threads, comments, or feedback\n  that must be fetched, fixed, replied to, marked, pushed,\n  and CI-verified. Triggers: \"handle PR reviews\", \"review comments\",\n  \"리뷰 대응\", \"レビュー対応\", \"ywc-handle-pr-reviews\". Do not use for\n  standalone feedback before PR automation (use ywc-receive-review), new PR\n  creation (use ywc-create-pr), doing the code review yourself (use\n  ywc-impl-review), review learnings (use ywc-review-learnings), or changes\n  outside open-PR context.\n---\n\n# Handle PR Review Health\n\n**Announce at start:** \"I'm using the ywc-handle-pr-reviews skill to run a PR health sweep across review artifacts, CI status, and merge-readiness.\"\n\nReview PR review artifacts, CI status, and merge-readiness blockers; fix issues where needed; and reply with an addressed marker for each comment-like artifact.\n\n## Rationalization Defense\n\nWhen tempted to skip a step, check this table first:\n\n| Excuse | Reality |\n|---|---|\n| \"This comment is just opinion, no fix needed\" | Even disagreement requires a reply explaining why. Silent skip looks like neglect. |\n| \"I'll batch all replies after fixing everything\" | Reply per thread as fixes land. Reviewers track which threads are resolved. |\n| \"Push without reply, the diff speaks for itself\" | Reviewers cannot tell intent from diff alone. Always pair fix with reply. |\n| \"Resolving the thread without reply is fine\" | Resolving without reply implies the reviewer's concern was wrong. Always state how it was addressed. |\n| \"Conflict in suggestions, pick one and move on\" | Surface the conflict to the user. Do not silently choose between reviewer A and reviewer B. |\n| \"PR not found for this branch, scan recent PRs\" | Stop and ask. Acting on a wrong PR overwrites unrelated reviewer threads. |\n| \"All review comments are addressed — CI is a separate concern\" | Fixes to source code (refactors, new imports, logic changes) can break CI. Always re-verify CI after pushing review fixes. A PR with all comments addressed but failing CI is still blocked from merging. |\n| \"The comments only needed replies, no code changed — so CI is fine to skip\" | CI can already be red for reasons unrelated to the comments (a flaky earlier push, a base-branch change, a dependency break). Handling a PR means leaving it mergeable. Always check current CI status when handling a PR, even when your replies pushed no code. |\n| \"CI is green and comments are addressed — the PR is mergeable\" | While the review was in progress the base branch may have advanced and the PR may now be `CONFLICTING`. Handling a PR means leaving it mergeable, which requires checking `gh pr view --json mergeable,mergeStateStatus`, not just CI. A conflicting PR is blocked from merge regardless of how many comments were resolved. |\n| \"The PR conflicts with base — rebase the branch to clear it\" | Rebasing rewrites SHAs and orphans the very review threads you are replying to. Merge the base *into* the feature branch (`git merge --no-ff origin\u002F\u003Cbase>`) instead. See `..\u002Freferences\u002Fpr-conflict-resolution.md`. |\n| \"The poller found a top-level review\u002Fcheck, but the line-comment script returned empty\" | Top-level reviews, PR comments, and review-like checks are first-class review artifacts. Fetch the artifact list and block merge until each one is fixed, answered, or explicitly deferred. |\n| \"I replied but did not include the marker\" | The polling gate is marker-based for non-threaded artifacts. Every reply must include `\u003C!-- \u003Creview_comment_addressed:\u003Cfingerprint>> -->` so the next poll can distinguish handled feedback from unresolved feedback. |\n\n**Violating the letter of these rules is violating the spirit.** Code review is a conversation, not a checklist.\n\n## Context\n\n- Current branch: !`git branch --show-current`\n- Recent commits: !`git log --oneline -5`\n\n## Arguments\n\n- `PR#`: supplied PR number, optional in the existing no-flag workflow.\n- `--worktree`: opt into a clean same-repository PR head worktree; requires the explicit number. Without it, preserve the existing workflow and do not create or switch worktrees.\n\n## Task\n\nFollow the steps below to handle PR review comments.\n\n### 1. Identify PR Number\n\n- Without `--worktree`, use a supplied PR number or identify the current branch's PR with `gh pr view --json number`; stop if no PR exists.\n- With `--worktree`, require an explicit positive PR number matching `^[1-9][0-9]*$` before lookup or mutation; missing\u002Finvalid input returns `NEEDS_CONTEXT`.\n- Pin the validated `PR_NUMBER` and repository identity for the invocation. Every later artifact\u002Freply\u002FCI\u002Fmerge-readiness command uses that number, never a fresh branch\u002Fcwd lookup.\n\nResolve `{owner}\u002F{repo}` dynamically at this stage — it's used throughout the workflow:\n\n```bash\nREPOSITORY=$(gh repo view --json nameWithOwner --jq .nameWithOwner)\n```\n\n### 1.5 Select and guard the PR worktree (`--worktree` only)\n\nFor `--worktree`, read [references\u002Fpr-worktree-identity.md](references\u002Fpr-worktree-identity.md) before any review read or mutation. It owns pinned same-repository\u002Fopen\u002Fhead validation, canonical in-place\u002Freused\u002Fcreated selection, exact fetch\u002Ffast-forward, one cwd re-entry, and failure preservation. An owner\u002Finput\u002Foutput\u002Fstatus mismatch returns `NEEDS_CONTEXT`. Without the flag, skip this section.\n\n### 2. Retrieve PR Health Artifacts\n\nIn worktree mode, run the identity\u002Fcwd guard first and pass the pinned `PR_NUMBER` and repository to the fetcher. Retrieve review artifacts, CI status, and merge-readiness in one normalized artifact list. Review artifacts may be empty; that is not terminal success. Continue through CI status and merge-readiness gates because a PR with no comments can still be blocked by failed checks or conflicts.\n\n```bash\nRESOLVER_LAUNCHER=\"$(bash \"${CODEX_HOME:-$HOME\u002F.codex}\u002Fskills\u002Fscripts\u002Fselect-resolver-launcher.sh\" 2>&1)\" || { echo \"BLOCKED: ${RESOLVER_LAUNCHER#BLOCKED: }\" >&2; exit 3; }\nFETCH_ARTIFACTS_SCRIPT=\"$(bash \"$RESOLVER_LAUNCHER\" \"ywc-handle-pr-reviews\u002Fscripts\u002Ffetch-pr-review-artifacts.sh\" bash)\" || exit $?\nbash \"$FETCH_ARTIFACTS_SCRIPT\" \\\n  {owner}\u002F{repo} {pr_number}\n# exit 0 -> normalized JSON artifact array on stdout (may have empty review artifacts)\n# exit 2 -> usage error\n# exit 3 -> gh CLI or GitHub API failure\n```\n\nThe script fetches unresolved review threads, PR comments, review submissions, `statusCheckRollup`, `mergeable`, `mergeStateStatus`, and PR `url`. It emits a normalized JSON array. Each artifact includes `artifact_type`, `fingerprint`, `reply_api`, `body`, `path`, `line`, `user`, and `state` where applicable. Comment-like artifacts use `artifact_type` values such as `review_thread`, `pr_comment`, and `review_submission`; CI artifacts use `status_check`; merge blockers use `merge_readiness`.\n\nIf no comment-like review artifacts are present, continue to Step 6.5 and Step 6.6 rather than reporting success early.\n\n### 3. Group and Analyze Review Artifacts\n\nBefore fixing anything, group all remaining comment-like review artifacts by file. Processing file-by-file is more efficient — you read each file once, apply all related fixes together, and create one coherent commit per file instead of jumping back and forth.\n\n**Processing strategy:**\n\n1. Collect all unresolved comment-like artifacts and group by target file path\n2. For each file, read the file once and analyze all related comments together\n3. Apply fixes for that file and commit as a unit\n4. Move to the next file\n5. Keep `status_check` and `merge_readiness` artifacts out of marker replies; resolve them by making the check pass or clearing the merge blocker.\n\n### 4. Classify and Fix Comments\n\nFor each comment, classify it into one of these categories:\n\n| Category                                                                                                   | Action                                                                                                                                                                                  |\n| ---------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| **Approval \u002F Acknowledgment** (tagged `review_comment_addressed`)                                          | Skip — already resolved                                                                                                                                                                 |\n| **Clear code change request** (the fix is straightforward and unambiguous)                                 | Apply the fix                                                                                                                                                                           |\n| **Controversial or ambiguous change request** (disagreement, architectural concern, or trade-off involved) | Do NOT auto-fix. Present the comment to the user with context, explain the trade-off, and ask for a decision. Reviewer feedback deserves thoughtful consideration, not blind acceptance |\n| **Question only** (no code change implied)                                                                 | Reply with an explanation — no fix needed                                                                                                                                               |\n\n**Security guardrails (never auto-apply, always defer to user):**\n\n- Removal of authentication, authorization, or security middleware\n- Addition of `eval()`, `exec()`, or dynamic code execution\n- Disabling RLS, bypassing tenant isolation, or weakening input validation\n- Hardcoded credentials or secrets\n\n**When applying fixes:**\n\n- Read the target file and identify the exact problem area referenced by the comment\n- Apply the minimal fix that addresses the reviewer's concern\n- If the comment references outdated code (the file has changed since the review), check whether the concern still applies to the current code. If it does, fix the current version. If not, reply explaining the code has already changed\n\n**Commit rules:**\n\n- One commit per file (group all fixes for the same file into a single commit)\n- Use commit message format: `fix: summary of the fix`\n- Push to remote after all commits are ready — pushing once at the end is cleaner than pushing after each commit\n\nWith `--worktree`, guard identity first and use only `git push origin \"HEAD:refs\u002Fheads\u002F$H\"`, including an approved review retry or base-merge update. On any required command failure, stop further retries and mutations; report each commit or push already completed and the failed gate.\n\n### 5. Reply to Comments\n\n**Attitude layer (mandatory)**: every reply must go through the discipline defined in `ywc-receive-review` — verify each artifact against the codebase before agreeing; replies state the fix or a technical pushback ending in a question; the forbidden vocabulary list (\"You're absolutely right!\", \"Great point!\", \"Thanks!\") applies to all `body` content surfaced via the reply API below.\n\nReply to every processed artifact that has `reply_api != \"none\"` so the reviewer knows the feedback was addressed. Every reply must include the exact marker for that artifact:\n\n```markdown\n\u003C!-- \u003Creview_comment_addressed:{fingerprint}> -->\n```\n\nFor `review_thread`, use the thread reply API to keep conversations organized:\n\n```bash\ngh api repos\u002F{owner}\u002F{repo}\u002Fpulls\u002F{pull_number}\u002Fcomments\u002F{in_reply_to_id}\u002Freplies -F body=@- \u003C\u003C'REPLY_BODY'\n...\nREPLY_BODY\n```\n\nFor `pr_comment` and `review_submission`, add a PR-level comment that references the artifact author\u002Ftype and includes the marker:\n\n```bash\ngh pr comment {pull_number} --body-file -\n```\n\nFor `status_check`, do not add a marker-only reply unless no code change is needed and the check is known to be a false positive. A failed review-like status check normally remains unresolved until the check passes.\n\n**Reply language:** Match the language of the original comment. If the reviewer wrote in Korean, reply in Korean. If in English, reply in English. If in Japanese, reply in Japanese. If in Chinese, reply in Simplified Chinese unless the reviewer used another Chinese locale. If in Spanish, reply in Spanish. Do not translate code suggestions, command output, file paths, API names, or quoted reviewer text.\n\n**Reply format by category:**\n\n- **Fixed:**\n  ```markdown\n  \u003C!-- \u003Creview_comment_addressed:{fingerprint}> -->\n  Fixed: [commit-hash](https:\u002F\u002Fgithub.com\u002F{owner}\u002F{repo}\u002Fpull\u002F{pr}\u002Fcommits\u002F{full_sha})\n  Description of what was changed and why\n  ```\n- **Deferred to user:** Do not include the marker before the user decides; return `NEEDS_CONTEXT` with the artifact `fingerprint`, reviewer, and trade-off.\n- **No fix needed:** Include the marker and explain the reasoning (e.g., intentional design choice, already handled elsewhere)\n- **Outdated comment:** Include the marker and explain why the concern no longer applies.\n\n### 6. Error Handling\n\nThings can go wrong during the process. Handle these gracefully:\n\n| Error                                 | How to handle                                                                           |\n| ------------------------------------- | --------------------------------------------------------------------------------------- |\n| `gh pr view` fails (no PR for branch) | Stop and tell the user. Don't guess the PR number                                       |\n| Push fails (non-fast-forward, remote feature branch advanced) | Without `--worktree`, retain `git pull --rebase origin \u003Cfeature-branch>` then re-push; never force-push without approval. With `--worktree`, stop retries and later mutations, return `BLOCKED`, and report prior commits\u002Fpushes. See `..\u002Freferences\u002Fpr-conflict-resolution.md` |\n| Comment reply API returns 403\u002F404     | Without `--worktree`, log\u002Fskip\u002Freport the reply. With `--worktree`, stop later mutations and return `BLOCKED` with prior side effects                      |\n| Referenced file no longer exists      | Reply to the comment explaining the file was removed, and skip the fix                  |\n\n### 6.5 CI Status Check & Fix\n\n**Always run this step — do not skip it, even when your replies pushed no code.** A PR review thread and CI status are two independent blockers on the same PR. Addressing every comment but leaving CI red still leaves the PR unmergeable, so handling a PR means checking both. This step covers two cases at once: CI regressions introduced by the fixes in Step 4, **and** pre-existing CI failures that were already red before you touched the PR (a flaky earlier push, a base-branch change, a broken dependency).\n\n```bash\n# Keep the PR_NUMBER resolved in Step 1; never rediscover it here.\n# With --worktree, run the guard before each check\u002Fwait.\ngh pr checks \"$PR_NUMBER\" --repo \"$REPOSITORY\"\n# exit 0 = all checks passed; non-zero = one or more checks failed or are pending\n```\n\nFor `--worktree`, a required CI command error or failed check is terminal: return `BLOCKED`, stop subsequent mutations\u002Fretries, and report prior commits\u002Fpushes. A successfully parsed pending state may be watched under the same guard. The repair-attempt path below applies only without `--worktree`.\n\n- **All checks pass**: proceed to Step 7.\n- **Checks still pending**: wait for completion with `gh pr checks \"$PR_NUMBER\" --repo \"$REPOSITORY\" --watch`, then re-evaluate.\n- **Any check fails**:\n  1. Get failure logs:\n     ```bash\n     gh run list --branch $(git branch --show-current) \\\n       --json databaseId,conclusion \\\n       --jq '.[] | select(.conclusion == \"failure\") | .databaseId' | head -1\n     gh run view \u003Crun-id> --log-failed\n     ```\n  2. Categorize and fix:\n     | Failure type | Fix action |\n     |---|---|\n     | Lint \u002F format | Run the project's auto-fix command, commit, push |\n     | Type \u002F test \u002F build | Analyze output, fix implementation, commit, push |\n     | Infra \u002F flaky \u002F clearly unrelated to this PR's scope | Do **not** blindly patch. Surface the failing check and logs to the user and ask how to proceed (e.g., re-run the job, or fix in a separate PR) |\n  3. Re-check CI after each push. Up to **2 fix attempts**.\n  4. If CI still fails after 2 attempts: record the failing check names in Step 7's summary and set the overall outcome to `DONE_WITH_CONCERNS` (not `DONE`).\n\n### 6.6 Merge-Readiness (Conflict) Check\n\n**Always run this step.** CI green and all comments addressed still does not guarantee the PR can merge — while the review was in progress the base branch may have advanced into a conflict. A PR review thread, CI status, and merge-readiness are three independent blockers on the same PR; handling a PR means leaving all three clear.\n\nFor `--worktree`, retain pinned `PR_NUMBER`\u002F`H`, apply the guard before every API\u002Fread\u002Fupdate\u002FCI operation, and use the explicit push refspec. Skip any current-branch PR-number rediscovery in the reference; a required failure stops the flow.\n\n> **Action required**: Read [`..\u002Freferences\u002Fpr-conflict-resolution.md`](..\u002Freferences\u002Fpr-conflict-resolution.md) before proceeding — it defines the `mergeable` \u002F `mergeStateStatus` semantics and the merge-not-rebase update procedure.\n\n```bash\ngh pr view \"$PR_NUMBER\" --repo \"$REPOSITORY\" --json number,state,headRefName,mergeable,mergeStateStatus --jq '{number, state, headRefName, mergeable, mergeStateStatus}'\n```\n\nWith `--worktree`, a `state` other than `OPEN` or a `headRefName` other than the pinned `H` is `BLOCKED` before any merge-readiness action or push.\n\n- `MERGEABLE` \u002F `CLEAN` → proceed to Step 7.\n- `BEHIND` → the branch is merely out of date (no textual conflict). Follow **Update Branch From Base** (merge the base into the feature branch — never rebase, since that orphans the review threads you just replied to), push, and re-verify CI (one additional cycle).\n- `CONFLICTING` \u002F `DIRTY` → follow **Update Branch From Base** in the reference. If it auto-resolves, push and re-verify CI (one additional cycle). If it reports real textual conflicts, surface the conflicting files + PR URL to the user, stop, and set the outcome to `BLOCKED` — do not auto-resolve or force-push.\n- `BLOCKED` → a required check or review gate is missing — **not** a conflict. Do not run the base-merge procedure; surface which required check or review is outstanding and set the outcome to `BLOCKED`.\n- `UNKNOWN` → poll briefly per the reference, then re-read.\n\n### 7. Final Summary\n\nReport the results so the user has a clear picture of what happened:\n\n- Total review artifacts processed vs skipped\n- CI status outcome and any status_check artifacts handled\n- Merge-readiness outcome and any merge_readiness artifacts handled\n- List of applied fixes with file paths and commit hashes\n- Any artifacts deferred to the user (with links)\n- Any errors encountered during the process\n- With `--worktree`, include the canonical path and `created` \u002F `reused` \u002F `in-place` state. Only `created` gets separate cleanup guidance from the saved canonical main checkout, after verifying the same resolved root\u002Fpath: `ywc-worktrees --mode prune --task-name \"pr-$PR_NUMBER\" --branch \"$H\" --keep-branch` guidance. Never auto-delete reused\u002Fin-place worktrees; preserve the PR head branch.\n- A retained review worktree may be `Leaked` in a later executor audit. Preserve audit classifications and resolve review-owned paths with their owner before another lifecycle.\n\n## Notes\n\n- Follow any additional instructions in `$ARGUMENTS`\n- When in doubt about a reviewer's intent, ask the user rather than guessing — misinterpreting feedback wastes more time than a quick clarification\n\n## Output Format\n\nReturn a PR review handling report:\n\n```text\nStatus: \u003CDONE | DONE_WITH_CONCERNS | BLOCKED | NEEDS_CONTEXT>\nPR: \u003Cnumber or URL>\nWorktree path: \u003Ccanonical path or N\u002FA>\nWorktree state: created | reused | in-place | N\u002FA\nProcessed: \u003Ccount and source of comments handled>\nSkipped: \u003Ccomments deferred with reason>\nValidation: \u003Ctests or CI checks rerun; CI status; merge-readiness>\nNext action: \u003Cremaining review\u002FCI action or \"none\">\n```\n\n## Validation\n\nBefore finalizing, verify that every actionable comment-like artifact is either addressed or explicitly deferred, reviewer intent was not guessed when ambiguous, fixes stay within PR scope, CI status is green or explicitly reported, and merge-readiness is clean or explicitly reported.\n\n## Integration\n\n- **upstream**: ywc-create-pr (a PR must exist before review comments can be handled); ywc-sequential-executor \u002F ywc-parallel-executor (executors that generate the PRs being reviewed)\n- **conditional provider**: `ywc-worktrees` supplies existing-head creation after the caller validates\u002Fpins the PR and selects no reusable path.\n- **downstream**: None — this skill closes the PR review loop; subsequent work is driven by the reviewer's approval or further comments\n","# Handle PR Review Health\n\n**Announce at start:** \"I'm using the ywc-handle-pr-reviews skill to run a PR health sweep across review artifacts, CI status, and merge-readiness.\"\n\nReview PR review artifacts, CI status, and merge-readiness blockers; fix issues where needed; and reply with an addressed marker for each comment-like artifact.\n\n## Rationalization Defense\n\nWhen tempted to skip a step, check this table first:\n\n| Excuse | Reality |\n|---|---|\n| \"This comment is just opinion, no fix needed\" | Even disagreement requires a reply explaining why. Silent skip looks like neglect. |\n| \"I'll batch all replies after fixing everything\" | Reply per thread as fixes land. Reviewers track which threads are resolved. |\n| \"Push without reply, the diff speaks for itself\" | Reviewers cannot tell intent from diff alone. Always pair fix with reply. |\n| \"Resolving the thread without reply is fine\" | Resolving without reply implies the reviewer's concern was wrong. Always state how it was addressed. |\n| \"Conflict in suggestions, pick one and move on\" | Surface the conflict to the user. Do not silently choose between reviewer A and reviewer B. |\n| \"PR not found for this branch, scan recent PRs\" | Stop and ask. Acting on a wrong PR overwrites unrelated reviewer threads. |\n| \"All review comments are addressed — CI is a separate concern\" | Fixes to source code (refactors, new imports, logic changes) can break CI. Always re-verify CI after pushing review fixes. A PR with all comments addressed but failing CI is still blocked from merging. |\n| \"The comments only needed replies, no code changed — so CI is fine to skip\" | CI can already be red for reasons unrelated to the comments (a flaky earlier push, a base-branch change, a dependency break). Handling a PR means leaving it mergeable. Always check current CI status when handling a PR, even when your replies pushed no code. |\n| \"CI is green and comments are addressed — the PR is mergeable\" | While the review was in progress the base branch may have advanced and the PR may now be `CONFLICTING`. Handling a PR means leaving it mergeable, which requires checking `gh pr view --json mergeable,mergeStateStatus`, not just CI. A conflicting PR is blocked from merge regardless of how many comments were resolved. |\n| \"The PR conflicts with base — rebase the branch to clear it\" | Rebasing rewrites SHAs and orphans the very review threads you are replying to. Merge the base *into* the feature branch (`git merge --no-ff origin\u002F\u003Cbase>`) instead. See `..\u002Freferences\u002Fpr-conflict-resolution.md`. |\n| \"The poller found a top-level review\u002Fcheck, but the line-comment script returned empty\" | Top-level reviews, PR comments, and review-like checks are first-class review artifacts. Fetch the artifact list and block merge until each one is fixed, answered, or explicitly deferred. |\n| \"I replied but did not include the marker\" | The polling gate is marker-based for non-threaded artifacts. Every reply must include `\u003C!-- \u003Creview_comment_addressed:\u003Cfingerprint>> -->` so the next poll can distinguish handled feedback from unresolved feedback. |\n\n**Violating the letter of these rules is violating the spirit.** Code review is a conversation, not a checklist.\n\n## Context\n\n- Current branch: !`git branch --show-current`\n- Recent commits: !`git log --oneline -5`\n\n## Arguments\n\n- `PR#`: supplied PR number, optional in the existing no-flag workflow.\n- `--worktree`: opt into a clean same-repository PR head worktree; requires the explicit number. Without it, preserve the existing workflow and do not create or switch worktrees.\n\n## Task\n\nFollow the steps below to handle PR review comments.\n\n### 1. Identify PR Number\n\n- Without `--worktree`, use a supplied PR number or identify the current branch's PR with `gh pr view --json number`; stop if no PR exists.\n- With `--worktree`, require an explicit positive PR number matching `^[1-9][0-9]*$` before lookup or mutation; missing\u002Finvalid input returns `NEEDS_CONTEXT`.\n- Pin the validated `PR_NUMBER` and repository identity for the invocation. Every later artifact\u002Freply\u002FCI\u002Fmerge-readiness command uses that number, never a fresh branch\u002Fcwd lookup.\n\nResolve `{owner}\u002F{repo}` dynamically at this stage — it's used throughout the workflow:\n\n```bash\nREPOSITORY=$(gh repo view --json nameWithOwner --jq .nameWithOwner)\n```\n\n### 1.5 Select and guard the PR worktree (`--worktree` only)\n\nFor `--worktree`, read [references\u002Fpr-worktree-identity.md](references\u002Fpr-worktree-identity.md) before any review read or mutation. It owns pinned same-repository\u002Fopen\u002Fhead validation, canonical in-place\u002Freused\u002Fcreated selection, exact fetch\u002Ffast-forward, one cwd re-entry, and failure preservation. An owner\u002Finput\u002Foutput\u002Fstatus mismatch returns `NEEDS_CONTEXT`. Without the flag, skip this section.\n\n### 2. Retrieve PR Health Artifacts\n\nIn worktree mode, run the identity\u002Fcwd guard first and pass the pinned `PR_NUMBER` and repository to the fetcher. Retrieve review artifacts, CI status, and merge-readiness in one normalized artifact list. Review artifacts may be empty; that is not terminal success. Continue through CI status and merge-readiness gates because a PR with no comments can still be blocked by failed checks or conflicts.\n\n```bash\nRESOLVER_LAUNCHER=\"$(bash \"${CODEX_HOME:-$HOME\u002F.codex}\u002Fskills\u002Fscripts\u002Fselect-resolver-launcher.sh\" 2>&1)\" || { echo \"BLOCKED: ${RESOLVER_LAUNCHER#BLOCKED: }\" >&2; exit 3; }\nFETCH_ARTIFACTS_SCRIPT=\"$(bash \"$RESOLVER_LAUNCHER\" \"ywc-handle-pr-reviews\u002Fscripts\u002Ffetch-pr-review-artifacts.sh\" bash)\" || exit $?\nbash \"$FETCH_ARTIFACTS_SCRIPT\" \\\n  {owner}\u002F{repo} {pr_number}\n# exit 0 -> normalized JSON artifact array on stdout (may have empty review artifacts)\n# exit 2 -> usage error\n# exit 3 -> gh CLI or GitHub API failure\n```\n\nThe script fetches unresolved review threads, PR comments, review submissions, `statusCheckRollup`, `mergeable`, `mergeStateStatus`, and PR `url`. It emits a normalized JSON array. Each artifact includes `artifact_type`, `fingerprint`, `reply_api`, `body`, `path`, `line`, `user`, and `state` where applicable. Comment-like artifacts use `artifact_type` values such as `review_thread`, `pr_comment`, and `review_submission`; CI artifacts use `status_check`; merge blockers use `merge_readiness`.\n\nIf no comment-like review artifacts are present, continue to Step 6.5 and Step 6.6 rather than reporting success early.\n\n### 3. Group and Analyze Review Artifacts\n\nBefore fixing anything, group all remaining comment-like review artifacts by file. Processing file-by-file is more efficient — you read each file once, apply all related fixes together, and create one coherent commit per file instead of jumping back and forth.\n\n**Processing strategy:**\n\n1. Collect all unresolved comment-like artifacts and group by target file path\n2. For each file, read the file once and analyze all related comments together\n3. Apply fixes for that file and commit as a unit\n4. Move to the next file\n5. Keep `status_check` and `merge_readiness` artifacts out of marker replies; resolve them by making the check pass or clearing the merge blocker.\n\n### 4. Classify and Fix Comments\n\nFor each comment, classify it into one of these categories:\n\n| Category                                                                                                   | Action                                                                                                                                                                                  |\n| ---------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| **Approval \u002F Acknowledgment** (tagged `review_comment_addressed`)                                          | Skip — already resolved                                                                                                                                                                 |\n| **Clear code change request** (the fix is straightforward and unambiguous)                                 | Apply the fix                                                                                                                                                                           |\n| **Controversial or ambiguous change request** (disagreement, architectural concern, or trade-off involved) | Do NOT auto-fix. Present the comment to the user with context, explain the trade-off, and ask for a decision. Reviewer feedback deserves thoughtful consideration, not blind acceptance |\n| **Question only** (no code change implied)                                                                 | Reply with an explanation — no fix needed                                                                                                                                               |\n\n**Security guardrails (never auto-apply, always defer to user):**\n\n- Removal of authentication, authorization, or security middleware\n- Addition of `eval()`, `exec()`, or dynamic code execution\n- Disabling RLS, bypassing tenant isolation, or weakening input validation\n- Hardcoded credentials or secrets\n\n**When applying fixes:**\n\n- Read the target file and identify the exact problem area referenced by the comment\n- Apply the minimal fix that addresses the reviewer's concern\n- If the comment references outdated code (the file has changed since the review), check whether the concern still applies to the current code. If it does, fix the current version. If not, reply explaining the code has already changed\n\n**Commit rules:**\n\n- One commit per file (group all fixes for the same file into a single commit)\n- Use commit message format: `fix: summary of the fix`\n- Push to remote after all commits are ready — pushing once at the end is cleaner than pushing after each commit\n\nWith `--worktree`, guard identity first and use only `git push origin \"HEAD:refs\u002Fheads\u002F$H\"`, including an approved review retry or base-merge update. On any required command failure, stop further retries and mutations; report each commit or push already completed and the failed gate.\n\n### 5. Reply to Comments\n\n**Attitude layer (mandatory)**: every reply must go through the discipline defined in `ywc-receive-review` — verify each artifact against the codebase before agreeing; replies state the fix or a technical pushback ending in a question; the forbidden vocabulary list (\"You're absolutely right!\", \"Great point!\", \"Thanks!\") applies to all `body` content surfaced via the reply API below.\n\nReply to every processed artifact that has `reply_api != \"none\"` so the reviewer knows the feedback was addressed. Every reply must include the exact marker for that artifact:\n\n```markdown\n\u003C!-- \u003Creview_comment_addressed:{fingerprint}> -->\n```\n\nFor `review_thread`, use the thread reply API to keep conversations organized:\n\n```bash\ngh api repos\u002F{owner}\u002F{repo}\u002Fpulls\u002F{pull_number}\u002Fcomments\u002F{in_reply_to_id}\u002Freplies -F body=@- \u003C\u003C'REPLY_BODY'\n...\nREPLY_BODY\n```\n\nFor `pr_comment` and `review_submission`, add a PR-level comment that references the artifact author\u002Ftype and includes the marker:\n\n```bash\ngh pr comment {pull_number} --body-file -\n```\n\nFor `status_check`, do not add a marker-only reply unless no code change is needed and the check is known to be a false positive. A failed review-like status check normally remains unresolved until the check passes.\n\n**Reply language:** Match the language of the original comment. If the reviewer wrote in Korean, reply in Korean. If in English, reply in English. If in Japanese, reply in Japanese. If in Chinese, reply in Simplified Chinese unless the reviewer used another Chinese locale. If in Spanish, reply in Spanish. Do not translate code suggestions, command output, file paths, API names, or quoted reviewer text.\n\n**Reply format by category:**\n\n- **Fixed:**\n  ```markdown\n  \u003C!-- \u003Creview_comment_addressed:{fingerprint}> -->\n  Fixed: [commit-hash](https:\u002F\u002Fgithub.com\u002F{owner}\u002F{repo}\u002Fpull\u002F{pr}\u002Fcommits\u002F{full_sha})\n  Description of what was changed and why\n  ```\n- **Deferred to user:** Do not include the marker before the user decides; return `NEEDS_CONTEXT` with the artifact `fingerprint`, reviewer, and trade-off.\n- **No fix needed:** Include the marker and explain the reasoning (e.g., intentional design choice, already handled elsewhere)\n- **Outdated comment:** Include the marker and explain why the concern no longer applies.\n\n### 6. Error Handling\n\nThings can go wrong during the process. Handle these gracefully:\n\n| Error                                 | How to handle                                                                           |\n| ------------------------------------- | --------------------------------------------------------------------------------------- |\n| `gh pr view` fails (no PR for branch) | Stop and tell the user. Don't guess the PR number                                       |\n| Push fails (non-fast-forward, remote feature branch advanced) | Without `--worktree`, retain `git pull --rebase origin \u003Cfeature-branch>` then re-push; never force-push without approval. With `--worktree`, stop retries and later mutations, return `BLOCKED`, and report prior commits\u002Fpushes. See `..\u002Freferences\u002Fpr-conflict-resolution.md` |\n| Comment reply API returns 403\u002F404     | Without `--worktree`, log\u002Fskip\u002Freport the reply. With `--worktree`, stop later mutations and return `BLOCKED` with prior side effects                      |\n| Referenced file no longer exists      | Reply to the comment explaining the file was removed, and skip the fix                  |\n\n### 6.5 CI Status Check & Fix\n\n**Always run this step — do not skip it, even when your replies pushed no code.** A PR review thread and CI status are two independent blockers on the same PR. Addressing every comment but leaving CI red still leaves the PR unmergeable, so handling a PR means checking both. This step covers two cases at once: CI regressions introduced by the fixes in Step 4, **and** pre-existing CI failures that were already red before you touched the PR (a flaky earlier push, a base-branch change, a broken dependency).\n\n```bash\n# Keep the PR_NUMBER resolved in Step 1; never rediscover it here.\n# With --worktree, run the guard before each check\u002Fwait.\ngh pr checks \"$PR_NUMBER\" --repo \"$REPOSITORY\"\n# exit 0 = all checks passed; non-zero = one or more checks failed or are pending\n```\n\nFor `--worktree`, a required CI command error or failed check is terminal: return `BLOCKED`, stop subsequent mutations\u002Fretries, and report prior commits\u002Fpushes. A successfully parsed pending state may be watched under the same guard. The repair-attempt path below applies only without `--worktree`.\n\n- **All checks pass**: proceed to Step 7.\n- **Checks still pending**: wait for completion with `gh pr checks \"$PR_NUMBER\" --repo \"$REPOSITORY\" --watch`, then re-evaluate.\n- **Any check fails**:\n  1. Get failure logs:\n     ```bash\n     gh run list --branch $(git branch --show-current) \\\n       --json databaseId,conclusion \\\n       --jq '.[] | select(.conclusion == \"failure\") | .databaseId' | head -1\n     gh run view \u003Crun-id> --log-failed\n     ```\n  2. Categorize and fix:\n     | Failure type | Fix action |\n     |---|---|\n     | Lint \u002F format | Run the project's auto-fix command, commit, push |\n     | Type \u002F test \u002F build | Analyze output, fix implementation, commit, push |\n     | Infra \u002F flaky \u002F clearly unrelated to this PR's scope | Do **not** blindly patch. Surface the failing check and logs to the user and ask how to proceed (e.g., re-run the job, or fix in a separate PR) |\n  3. Re-check CI after each push. Up to **2 fix attempts**.\n  4. If CI still fails after 2 attempts: record the failing check names in Step 7's summary and set the overall outcome to `DONE_WITH_CONCERNS` (not `DONE`).\n\n### 6.6 Merge-Readiness (Conflict) Check\n\n**Always run this step.** CI green and all comments addressed still does not guarantee the PR can merge — while the review was in progress the base branch may have advanced into a conflict. A PR review thread, CI status, and merge-readiness are three independent blockers on the same PR; handling a PR means leaving all three clear.\n\nFor `--worktree`, retain pinned `PR_NUMBER`\u002F`H`, apply the guard before every API\u002Fread\u002Fupdate\u002FCI operation, and use the explicit push refspec. Skip any current-branch PR-number rediscovery in the reference; a required failure stops the flow.\n\n> **Action required**: Read [`..\u002Freferences\u002Fpr-conflict-resolution.md`](..\u002Freferences\u002Fpr-conflict-resolution.md) before proceeding — it defines the `mergeable` \u002F `mergeStateStatus` semantics and the merge-not-rebase update procedure.\n\n```bash\ngh pr view \"$PR_NUMBER\" --repo \"$REPOSITORY\" --json number,state,headRefName,mergeable,mergeStateStatus --jq '{number, state, headRefName, mergeable, mergeStateStatus}'\n```\n\nWith `--worktree`, a `state` other than `OPEN` or a `headRefName` other than the pinned `H` is `BLOCKED` before any merge-readiness action or push.\n\n- `MERGEABLE` \u002F `CLEAN` → proceed to Step 7.\n- `BEHIND` → the branch is merely out of date (no textual conflict). Follow **Update Branch From Base** (merge the base into the feature branch — never rebase, since that orphans the review threads you just replied to), push, and re-verify CI (one additional cycle).\n- `CONFLICTING` \u002F `DIRTY` → follow **Update Branch From Base** in the reference. If it auto-resolves, push and re-verify CI (one additional cycle). If it reports real textual conflicts, surface the conflicting files + PR URL to the user, stop, and set the outcome to `BLOCKED` — do not auto-resolve or force-push.\n- `BLOCKED` → a required check or review gate is missing — **not** a conflict. Do not run the base-merge procedure; surface which required check or review is outstanding and set the outcome to `BLOCKED`.\n- `UNKNOWN` → poll briefly per the reference, then re-read.\n\n### 7. Final Summary\n\nReport the results so the user has a clear picture of what happened:\n\n- Total review artifacts processed vs skipped\n- CI status outcome and any status_check artifacts handled\n- Merge-readiness outcome and any merge_readiness artifacts handled\n- List of applied fixes with file paths and commit hashes\n- Any artifacts deferred to the user (with links)\n- Any errors encountered during the process\n- With `--worktree`, include the canonical path and `created` \u002F `reused` \u002F `in-place` state. Only `created` gets separate cleanup guidance from the saved canonical main checkout, after verifying the same resolved root\u002Fpath: `ywc-worktrees --mode prune --task-name \"pr-$PR_NUMBER\" --branch \"$H\" --keep-branch` guidance. Never auto-delete reused\u002Fin-place worktrees; preserve the PR head branch.\n- A retained review worktree may be `Leaked` in a later executor audit. Preserve audit classifications and resolve review-owned paths with their owner before another lifecycle.\n\n## Notes\n\n- Follow any additional instructions in `$ARGUMENTS`\n- When in doubt about a reviewer's intent, ask the user rather than guessing — misinterpreting feedback wastes more time than a quick clarification\n\n## Output Format\n\nReturn a PR review handling report:\n\n```text\nStatus: \u003CDONE | DONE_WITH_CONCERNS | BLOCKED | NEEDS_CONTEXT>\nPR: \u003Cnumber or URL>\nWorktree path: \u003Ccanonical path or N\u002FA>\nWorktree state: created | reused | in-place | N\u002FA\nProcessed: \u003Ccount and source of comments handled>\nSkipped: \u003Ccomments deferred with reason>\nValidation: \u003Ctests or CI checks rerun; CI status; merge-readiness>\nNext action: \u003Cremaining review\u002FCI action or \"none\">\n```\n\n## Validation\n\nBefore finalizing, verify that every actionable comment-like artifact is either addressed or explicitly deferred, reviewer intent was not guessed when ambiguous, fixes stay within PR scope, CI status is green or explicitly reported, and merge-readiness is clean or explicitly reported.\n\n## Integration\n\n- **upstream**: ywc-create-pr (a PR must exist before review comments can be handled); ywc-sequential-executor \u002F ywc-parallel-executor (executors that generate the PRs being reviewed)\n- **conditional provider**: `ywc-worktrees` supplies existing-head creation after the caller validates\u002Fpins the PR and selects no reusable path.\n- **downstream**: None — this skill closes the PR review loop; subsequent work is driven by the reviewer's approval or further comments\n",{"name":5,"description":7},"main","7e8ac872e53df8c89d75663e031626281a2a2f5c","plugins\u002Fywc-agent-toolkit\u002Fskills\u002Fywc-handle-pr-reviews",1,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit","https:\u002F\u002Fgithub.com\u002Fyongwoon","https:\u002F\u002Fwww.webhani.com","2026-11-08 17:14:59",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add yongwoon\u002Fywc-agent-toolkit --skill ywc-handle-pr-reviews",{"tool":37,"command":38},"bunx","bunx skills add yongwoon\u002Fywc-agent-toolkit --skill ywc-handle-pr-reviews",{"tool":40,"command":41},"pnpm","pnpm dlx skills add yongwoon\u002Fywc-agent-toolkit --skill ywc-handle-pr-reviews","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fywc-agent-toolkit\u002Fskills\u002Fywc-handle-pr-reviews\u002FSKILL.md",true,[45,51,55,59,63,67,71,75,79,83,89,93],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",687,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fywc-agent-toolkit\u002Fskills\u002Fywc-handle-pr-reviews\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"evals\u002Fevals.json",3199,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fywc-agent-toolkit\u002Fskills\u002Fywc-handle-pr-reviews\u002Fevals\u002Fevals.json",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"README.en.md",1517,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fywc-agent-toolkit\u002Fskills\u002Fywc-handle-pr-reviews\u002FREADME.en.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"README.es.md",1996,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fywc-agent-toolkit\u002Fskills\u002Fywc-handle-pr-reviews\u002FREADME.es.md",{"path":64,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":65,"sourceHtmlUrl":66},"README.ja.md",1596,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fywc-agent-toolkit\u002Fskills\u002Fywc-handle-pr-reviews\u002FREADME.ja.md",{"path":68,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":69,"sourceHtmlUrl":70},"README.ko.md",1526,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fywc-agent-toolkit\u002Fskills\u002Fywc-handle-pr-reviews\u002FREADME.ko.md",{"path":72,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":73,"sourceHtmlUrl":74},"README.md",2531,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fywc-agent-toolkit\u002Fskills\u002Fywc-handle-pr-reviews\u002FREADME.md",{"path":76,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":77,"sourceHtmlUrl":78},"README.zh.md",1614,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fywc-agent-toolkit\u002Fskills\u002Fywc-handle-pr-reviews\u002FREADME.zh.md",{"path":80,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fpr-worktree-identity.md",6300,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fywc-agent-toolkit\u002Fskills\u002Fywc-handle-pr-reviews\u002Freferences\u002Fpr-worktree-identity.md",{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"scripts\u002Ffetch-pr-review-artifacts.sh","SCRIPT","脚本",6195,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fywc-agent-toolkit\u002Fskills\u002Fywc-handle-pr-reviews\u002Fscripts\u002Ffetch-pr-review-artifacts.sh",{"path":90,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":91,"sourceHtmlUrl":92},"scripts\u002Ffetch-unresolved-comments.sh",759,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fywc-agent-toolkit\u002Fskills\u002Fywc-handle-pr-reviews\u002Fscripts\u002Ffetch-unresolved-comments.sh",{"path":94,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":95,"sourceHtmlUrl":96},"scripts\u002Ftest_fetch_pr_review_artifacts.py",15636,"https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fywc-agent-toolkit\u002Fskills\u002Fywc-handle-pr-reviews\u002Fscripts\u002Ftest_fetch_pr_review_artifacts.py",[98,104,110,117,124,131],{"skillNo":99,"name":100,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":18},"01M72TQ84GTCPCV2VJ778V17TW","missing-frontmatter","https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fscripts\u002Ffixtures\u002Fcodex-description-limit\u002Fmissing-frontmatter\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":18},"01M72TQ6M4BFWE7P9EPW0GZDCM","malformed-frontmatter","https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fscripts\u002Ffixtures\u002Fcodex-description-limit\u002Fmalformed-frontmatter\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":18},"01M72TQ3ESGKXZ4QRWGTX92BKJ","fixture-501-fail","(ywc) Use when aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa Do not use for x.","https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fscripts\u002Ffixtures\u002Fcodex-description-limit\u002F501-fail\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":18},"01M72TQ0HJ8H3R37J9WPWGKJZR","fixture-500-pass","(ywc) Use when aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa Do not use for x.","https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fscripts\u002Ffixtures\u002Fcodex-description-limit\u002F500-pass\u002FSKILL.md",[],[],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":18},"01M72TPWNCC7NEYD0D9N12KSQS","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\u002Fdeletion 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.","https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fywc-agent-toolkit\u002Fskills\u002Fywc-worktrees\u002FSKILL.md",[],[],{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":18},"01M72TPRNR3E6QWB91GM98ABBV","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\u002Fdatabase writes outside the local Markdown map.","https:\u002F\u002Fgithub.com\u002Fyongwoon\u002Fywc-agent-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fywc-agent-toolkit\u002Fskills\u002Fywc-wayfinder\u002FSKILL.md",[],[]]