القائمة
Monitor GitHub Actions CI for the current PR/branch until it concludes, then report green/red with failure logs. Use when the user says "watch the CI", "is CI passing?", "monitor the checks", or after opening a PR and wanting to wait for checks. Pairs with commit-push-pr (before) and merge (after).
التثبيت باستخدام 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.
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.
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.
| name | watch |
| description | Monitor GitHub Actions CI for the current PR/branch until it concludes, then report green/red with failure logs. Use when the user says "watch the CI", "is CI passing?", "monitor the checks", or after opening a PR and wanting to wait for checks. Pairs with commit-push-pr (before) and merge (after). |
Follow the GitHub Actions checks for a PR until they finish, then summarize. Use the
GitHub MCP (mcp__github__*); resolve <OWNER>/<REPO> from
git remote get-url origin (this repo: qtmleap/Hono-Vite-Workers).
mcp__github__list_pull_requests(owner: '<OWNER>', repo: '<REPO>',
state:'open', head:'<OWNER>:<current-branch>')
git branch --show-current). Take the PR number.The MCP has no blocking --watch, so poll. Each tick, read the PR's checks:
mcp__github__pull_request_read(method:'get_check_runs', owner: '<OWNER>',
repo: '<REPO>', pullNumber:<pr>)
method:'get_status' for the combined commit status.in_progress/queued → still pending. If all completed
with conclusion: success → green. Any failure/cancelled/timed_out → red..github/workflows/integration.yaml): CommitLint and
Code Check (Biome + tsc + test). code_review.yaml (ChatGPT review) is advisory./loop, do one poll per tick and let the loop schedule
the interval. Otherwise re-poll roughly every 30s until it concludes./merge.get_check_runs (each run has a
name, conclusion, and details_url). Read its log to find the root cause —
gh run view <run-id> --log-failed is the simplest way to fetch Actions logs (the
MCP exposes check runs, not raw step logs). Surface the specific failing step (a
commitlint subject-case violation, a Biome lint error, a tsc error, a failing test)
and propose the fix. Do not merge.type is outside the .commitlintrc.yaml enum. Fix and re-push.