メニュー
Use when any GitHub PR workflow needs to checkout, inspect, review, test, or modify a PR locally without disturbing the current workspace; drive isolated review/fix worktree preparation, status checks, and safe cleanup through the bundled deterministic helper
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the user wants to inspect, classify, add, remove, replace, synchronize, or verify labels on a GitHub pull request; require evidence-backed current impact for bug, security, severity, and priority classifications, preserve unrelated labels, plan changes before applying them, and use the bundled REST-based helper for authorized mutations
Use when the user wants a maintainer-quality review of a GitHub PR, actionable findings, blocker or closure recommendations, or explicitly authorized COMMENT-only GitHub feedback; gate deep review on supported-path reachability and evidenced net value, report close/no-merge directly for unreachable or valueless changes, never approve PRs, and use pr-worktree for isolated local checkout
Use when the user explicitly wants to modify an existing GitHub PR as a maintainer and push focused fixes to its head branch; establish the confirmed issue, protected contract, minimal change cone, and verification evidence first; use pr-worktree so the current workspace is not disturbed
Safely rebase an existing GitHub pull request branch onto the latest base branch, resolve conflicts while preserving the PR's intent, rerun focused verification, and optionally update the remote PR branch. Use when the user asks to rebase, sync, refresh, or bring a PR up to date with main or another base branch, especially before merge or after the base branch changed.
Rewrite and polish Chinese technical writing through selective, comparative edits and relevant references, including author-approved samples, before/after pairs, voice profiles, factual sources, and platform examples. Use when the user asks to rewrite, polish, 润色, 改写, 提升吸引力, match their voice or 文风, improve readability, flow, rhythm, viewpoint, or narrative, while preserving facts, narrative ownership, author perspective, and technical substance.
Capture, incubate, and review verifiable content fragments from daily engineering work — debugging findings, experiments, tool comparisons, pitfalls — for future social posts. Use when the user says to save/log/capture a material or experience fragment, asks what content is ready to write, or wants to review accumulated material fragments by topic or maturity.
| name | pr-worktree |
| description | Use when any GitHub PR workflow needs to checkout, inspect, review, test, or modify a PR locally without disturbing the current workspace; drive isolated review/fix worktree preparation, status checks, and safe cleanup through the bundled deterministic helper |
Use the bundled script as the source of truth. It resolves PR metadata, selects the base remote, fetches current base/PR refs, chooses an ignored or sibling path, creates or safely reuses the worktree, and returns a machine-readable manifest. Do not make the LLM reconstruct that lifecycle with ad hoc shell commands.
gh pr checkout or switch branches in the user's current workspace.review mode for read/test/review work and fix mode only when the user authorized commits and pushes.workdir set to the manifest's worktree path.From any path inside the base repository:
python3 <this-skill>/scripts/pr_worktree.py prepare <PR-number-or-URL> --repo <OWNER/REPO> --mode review --format markdown
For maintainer edits:
python3 <this-skill>/scripts/pr_worktree.py prepare <PR-number-or-URL> --repo <OWNER/REPO> --mode fix --format markdown
Omit --repo when the current GitHub repository context is unambiguous. Useful overrides:
--repo-dir <path> when invoking outside the base repository root;--path <path> when an established worktree location is required;--remote <name> when remote URL auto-detection cannot select the base repository remote;--format json for orchestration.Read the manifest once. It provides:
match, local ahead, behind, or diverged);In review mode, the helper refuses a stale, behind, or diverged checkout. In fix mode it preserves a branch that is locally ahead of GitHub metadata, but refuses behind or diverged state so existing maintainer commits are never reset implicitly. For cross-repository fixes, treat maintainerCanModify: false as a warning that the eventual push may be rejected; do not change remotes or invent a replacement branch without user direction.
Set the tool workdir to the returned path. Use the returned base tracking ref for the three-dot diff. Do not fetch or rediscover metadata again unless the PR head changes while the task is active.
Before edits in fix mode, confirm:
git branch --show-current
git status --short --branch
git remote -v
The branch must be attached and tracked-clean. Untracked files may remain and must not be altered.
Use the helper instead of manually combining branch/head/dirty checks:
python3 <this-skill>/scripts/pr_worktree.py status --path <worktree-path> --format markdown
Only when the user requests cleanup:
python3 <this-skill>/scripts/pr_worktree.py cleanup --repo-dir <base-repository> --path <worktree-path> --format markdown
Cleanup refuses tracked changes, untracked files, attached branches without upstreams, and branches with unpushed commits. Prepare/reuse ignores untracked files, but cleanup preserves them rather than deleting them. Report the refusal; do not bypass it with --force or manual deletion.