菜单
Complete a pull request by monitoring CI checks and merging when ready. Use when: (1) User says 'complete pr', 'merge pr', or 'finish pr', (2) PR is reviewed and ready but CI may still be running, (3) User wants to wait for CI and auto-merge.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Sweep open GitHub issues — optionally narrowed by label — and drive each to completion via `/big-plan -m -a`. Collects candidates, triages out work that needs careful human judgment, confirms once, then handles the rest autonomously one issue at a time. Use when: (1) User says '/issue-sweep', 'sweep issues', 'sweep open issues', 'handle the open issues', 'clear the issue backlog', or 'do the issues', (2) The user wants to batch-process a label's worth of issues (e.g. `agent-found`, `mac`), (3) After a work round that left a pile of follow-up issues. Options: "`-f`/`--filter LABEL` keeps only issues carrying that label; `-ex`/`--exclude LABEL`" drops issues carrying it; with no options it sweeps ALL open issues. Locally-checkable "verify X" tasks are verified directly and closed (not run through `/big-plan`). Skips issues that need careful human judgment (huge multi-major version bumps, super-big epics, design calls); verification tasks that can't be auto-verified locally (auth/deploy/external/subjective) are
Generate or redesign raster images (PNG mockups, illustrations, photos, UI design polish) from inside Claude Code by driving Codex CLI's built-in $imagegen, billed to ChatGPT-included usage instead of per-image OpenAI API charges. Use whenever the user wants to create/generate an image, make a mockup or illustration, produce a photo, polish or redesign a UI from a screenshot, or get a PNG out of a session — even if they don't mention Codex or "imagegen". This is the preferred image-generation path because Anthropic models cannot generate raster images and this route avoids API billing.
Iterative visual design-polish loop for an existing or WIP web UI. Each round: capture the live page as screenshots, judge it from the rendered pixels, and apply CSS polish toward a better-looking target using /css-wisdom's tight-token strategy — then re-capture and compare. The target direction is set by codex-imagegen 'north-star' mockups generated from the current screenshot, so the loop pursues a genuinely better look instead of nudging the existing one in place. Use when: (1) user says 'design-polish-loop', 'polish loop', 'polish this page/design/UI', (2) user wants to level up / upgrade the look of a current design or WIP project, (3) user wants AI-proposed redesign directions applied to a real rendering page, (4) user calls a design plain, dated, flat, or unpolished and wants it improved. Main use case: improving the current design of a WIP project. It polishes what already renders — not brand-new-from-scratch pages.
Bump every `@takazudo/*` registry dependency in the current project to its newest version, resolving each by the channel it currently tracks. Use when: (1) User says '/dev-bump-zudo-deps', 'bump zudo deps', 'bump the @takazudo packages', 'update zfb', 'update zudo-doc', or 'update the takazudo toolchain to latest', (2) A new `@takazudo/*` prerelease or release has shipped and this project should adopt it, (3) Routine first-party dependency-update rounds. Resolution rule: a dep currently on the `next` prerelease line (`0.1.0-next.N`) → newest `next` release; a dep on the literal `latest` tag → `dist-tags.latest`; a plain stable semver → newest stable. Skips `workspace:`/`file:`/`link:` specs and leaves operator style (exact / `^` / `~`) and prerelease channel intact. A bundled script does the discovery + semver resolution; this skill drives install + verify + report.
Plan implementation by breaking work into one epic GitHub issue + child sub-issues. Use when: (1) User says '/big-plan', (2) User wants to plan an implementation before coding, (3) User wants to split a feature into small issues for parallel agent team work, (4) User references existing issues (e.g. 'implement issue #123', 'plan all open issues', 'plan recent 3 open issues'). Auto-reads project-scope l-lessons-* skills (from /retro-notes) before planning. Codex (-co) is the DEFAULT Step 5 plan reviewer — it runs even when no reviewer flag is passed; -op/-gco add more second opinions (runnable in parallel). Use -a/--auto to run the chain autonomously: skip the Step 6 confirmation wait (pausing only when something needs careful consideration), auto-create the issues, then auto-invoke the implementation skill in the same session — /x-wt-teams for a multi-sub-issue plan, /x-as-pr for a single-sub-issue plan — forwarding -a so multi-wave plans auto-chain wave after wave. Use -m/--merge to also merge the final PR i
Purge GitHub Actions caches across every non-archived repo for one or more GitHub owners (users or orgs). Use when (1) the user says "purge gh cache", "clear actions cache", "delete CI cache", or invokes /dev-purge-gh-cache, (2) the user wants to free up GitHub Actions cache storage for an account/org, (3) the user names one or more GitHub owners (e.g. "Takazudo", "zudolab") and asks to wipe their Actions caches. Handles fan-out across all repos, parallel survey, bulk delete, and real-time verification.
| name | pr-complete |
| description | Complete a pull request by monitoring CI checks and merging when ready. Use when: (1) User says 'complete pr', 'merge pr', or 'finish pr', (2) PR is reviewed and ready but CI may still be running, (3) User wants to wait for CI and auto-merge. |
| argument-hint | [-c/--close] [-k/--keep-issue] [-w/--watch-ci] [-now/--no-wait] |
This PR is checked, reviewed, and no other tasks are left. Complete the following:
On Claude Code on the web (
$CLAUDE_CODE_REMOTE=true): followweb/web-mode.md. Check CI, merge the PR, and close the linked issue via the GitHub MCP (pull_request_read/get_check_runs,merge_pull_request,issue_write), notgh. Branch deletion — see web-mode.md §5: when the PR's head is theclaude/*session branch (the common web case — head=$WEB_BASE, base=$WEB_PARENT), merge via MCPmerge_pull_requestWITHOUT any branch-delete (nodelete_branch:true). The web platform owns the session branch — never delete it. Deleting aclaude/agent-fix-*fix branch is fine; deleting the session branch is not. Translate the--delete-branchin Step 1 /--no-waitaccordingly: on web, drop the delete for the session branch.
Before anything else, run git status and git diff --stat to check for unstaged or staged-but-uncommitted changes.
/pr-complete./commits push to commit and push automatically, then continue to step 1./commits push first, then re-invoke /pr-complete." and stop here.gh pr view and gh pr checks--no-wait / -now was passed → skip the CI wait and merge immediately (see "--no-wait (-now) option" below)/watch-ci to monitor CI in the backgroundgh pr merge --merge --delete-branch (on web (web-mode.md §5): MCP merge_pull_request with NO branch-delete when the head is the claude/* session branch — the web owns it; only claude/agent-fix-* heads may be deleted)Important: Before merging, verify:
/watch-ci and stop), unless --no-wait was passedIf any CI checks fail, report the failure and do not merge (unless --no-wait was explicitly passed — see below).
--no-wait (-now) optionIf --no-wait or -now is passed, skip the CI watch entirely and merge the PR immediately, regardless of check status:
/watch-cigh pr merge --merge --delete-branch straight away--close / --keep-issue / --watch-ci) as normalWhen to use: the user has already verified locally that the changes are good (or doesn't care about CI for this merge) and wants the PR merged now without waiting on the pipeline. This is an explicit opt-in — never assume --no-wait from context.
Note: --no-wait only skips waiting for CI checks. The --watch-ci (-w) option, which watches post-merge CI on the target branch, is independent and still works alongside -now.
--close (-c) optionIf --close or -c is passed, after the PR is successfully merged:
gh pr view --json closingIssuesReferencesCheck if it is an epic issue (one that holds sub-issues):
a. Fetch the issue body: gh issue view <number> --json body
b. Look for task list entries referencing issues in the body:
Patterns: - [ ] #N, - [x] #N, - [ ] owner/repo#N, - [x] owner/repo#N
c. Also try the GitHub sub-issues API: gh api repos/{owner}/{repo}/issues/<number>/sub_issues
(this returns a list if the newer GitHub sub-issues feature is in use)
If sub-issues are found (either from the body task list or the API):
gh issue view <sub-issue-number> --json stategh issue close <sub-issue-number>gh issue close <number>If no sub-issues are found (regular issue):
gh issue close <number>--keep-issue (-k) optionIf --keep-issue or -k is passed, after the PR is successfully merged:
--close)[PR-Merged][Confirm] to the issue title:gh issue edit <number> --title "[PR-Merged][Confirm] <original title>"Note: --keep-issue and --close are mutually exclusive. If both are passed, --keep-issue takes precedence.
--watch-ci (-w) optionIf --watch-ci or -w is passed, after the PR is successfully merged:
gh run list --branch <base-branch> --limit 5 --json databaseId,name,status,conclusion/watch-ci to monitor the merge target branch CI in the background/watch-ci already handles merged PRs — it will detect the merged state and watch the target branch CIThis option is only activated when explicitly passed. Without -w, pr-complete does not watch post-merge CI.