菜单
Merge a feature→develop pull request once CI is green. Use when the user says "merge the PR", "merge if green", "land this", or after watch reports success. Verifies all checks pass and the branch is mergeable before merging; refuses on pending/failed checks. For develop→master production releases use the `release` skill instead.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Commit the current working tree on a feature branch (cut from develop), push it, and open a pull request into develop. Use when the user says "ship this", "make a PR", "commit and push and open a PR", or wants to turn local changes into a reviewable PR. Handles branch-first safety, commitlint-format messages, and the GitHub PR.
Prisma ORM with Cloudflare D1 — schema configuration, migration workflow, client setup, and deployment. Load when working with Prisma + D1 migrations, schema changes, or PrismaClient instantiation in Workers.
PWA implementation — Service Worker registration, cache strategies, update notification flow, and manifest setup. Load when adding PWA support, Service Worker caching, update prompts, offline fallback, or cache-invalidation logic to any web app.
Promote develop to master — open (or reuse) the develop→master PR, confirm CI is green, merge to master (which triggers the production Cloudflare deploy), then tag the release vX.Y.Z. Use when the user says "release", "cut a release", "promote develop to master", "ship to production". This is the ONLY path that touches master/production.
TanStack Query (React Query) best practices for data fetching, caching, mutations, and server state management. Activate when building data-driven React applications with server state.
Review and refactor UI components for better design, accessibility, and consistency. Loads ux-designer skill knowledge to evaluate and improve existing interfaces.
| name | merge |
| description | Merge a feature→develop pull request once CI is green. Use when the user says "merge the PR", "merge if green", "land this", or after watch reports success. Verifies all checks pass and the branch is mergeable before merging; refuses on pending/failed checks. For develop→master production releases use the `release` skill instead. |
Merge a PR (normally feature → develop) only after confirming CI passed and there
are no conflicts. Use the GitHub MCP (mcp__github__*); resolve <OWNER>/<REPO>
from git remote get-url origin (this repo: qtmleap/Hono-Vite-Workers).
Merging into
developdeploys to the development env — not production. A PR whose base ismasteris a release: stop and use thereleaseskill (it adds the production confirmation and the version tag).
mcp__github__list_pull_requests(owner: '<OWNER>', repo: '<REPO>', state:'open', head:'<OWNER>:<current-branch>').CI is green. mcp__github__pull_request_read(method:'get_check_runs', …, pullNumber:<pr>)
(and method:'get_status') — every required check conclusion: success. If anything
is queued/in_progress → wait (suggest /watch) and stop. Any failure → stop and
report; never merge a red PR.
Mergeable. mcp__github__pull_request_read(method:'get', …) → mergeable is true
and mergeable_state is clean (not dirty/blocked/behind). If behind base,
update first: mcp__github__update_pull_request_branch(owner, repo, pullNumber:<pr>).
Base must be develop. Confirm the PR's base.ref is develop (or another
feature/integration branch). If it targets master, this is a production release —
stop and switch to the release skill; do not merge it here.
mcp__github__merge_pull_request(
owner: '<OWNER>', repo: '<REPO>', pullNumber:<pr>,
merge_method:'squash',
commit_title:'<commitlint-style squash subject>')
commit_title must still satisfy commitlint (lowercase
start, valid type incl. chore, ≤ 96 chars).merge_pull_request has no delete-branch option — after a green merge, delete the
source branch separately: git push origin --delete <feature-branch> (deleting a
feature branch is fine; never delete/force master/develop).gh pr merge <pr> --squash --delete-branch.develop → master release (release skill).develop runs deployment.yaml against the development env; offer to
/watch it if the user wants to confirm the dev deploy.git switch develop && git pull.develop has accumulated the changes meant for production, run release to
promote it to master, deploy production, and tag vX.Y.Z.