watch

Estrelas0

Forks0

Atualizado4 de junho de 2026 às 19:26

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).

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

qtmleap

qtmleap/Hono-Vite-Workers

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

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).

watch — monitor CI to a conclusion

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).

Identify the target

Default to the PR for the current branch — find it by head:
```
mcp__github__list_pull_requests(owner: '<OWNER>', repo: '<REPO>',
  state:'open', head:'<OWNER>:<current-branch>')
```
(current branch = git branch --show-current). Take the PR number.
Accept an explicit PR number/URL if the user gives one.

Watch (poll loop)

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>)

Also method:'get_status' for the combined commit status.
Aggregate: if any check is in_progress/queued → still pending. If all completed with conclusion: success → green. Any failure/cancelled/timed_out → red.
This repo's required checks (.github/workflows/integration.yaml): CommitLint and Code Check (Biome + tsc + test). code_review.yaml (ChatGPT review) is advisory.
Pacing: if invoked inside /loop, do one poll per tick and let the loop schedule the interval. Otherwise re-poll roughly every 30s until it concludes.

On conclusion

All green → report success with the PR URL and suggest /merge.
Any failure → identify the failing check from 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.
Pending/stuck → report what is still queued.

Notes

Read-only: this skill never pushes, merges, or re-runs jobs unless the user asks.
A common red here is commitlint: the subject started with a capitalized English word (subject-case), or the type is outside the .commitlintrc.yaml enum. Fix and re-push.

Mais deste repositório

mesmo repositório

commit-push-pr

qtmleap/Hono-Vite-Workers

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.

2026-06-040

merge

qtmleap/Hono-Vite-Workers

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.

2026-06-040

prisma-d1

qtmleap/Hono-Vite-Workers

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.

2026-06-040

pwa

qtmleap/Hono-Vite-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.

2026-06-040

release

qtmleap/Hono-Vite-Workers

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.

2026-06-040

tanstack-query-best-practices

qtmleap/Hono-Vite-Workers

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.

2026-06-040

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).

watch — monitor CI to a conclusion

Identify the target

Default to the PR for the current branch — find it by head:
```
mcp__github__list_pull_requests(owner: '<OWNER>', repo: '<REPO>',
  state:'open', head:'<OWNER>:<current-branch>')
```
(current branch = git branch --show-current). Take the PR number.
Accept an explicit PR number/URL if the user gives one.

Watch (poll loop)

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>)

Also method:'get_status' for the combined commit status.
Aggregate: if any check is in_progress/queued → still pending. If all completed with conclusion: success → green. Any failure/cancelled/timed_out → red.
This repo's required checks (.github/workflows/integration.yaml): CommitLint and Code Check (Biome + tsc + test). code_review.yaml (ChatGPT review) is advisory.
Pacing: if invoked inside /loop, do one poll per tick and let the loop schedule the interval. Otherwise re-poll roughly every 30s until it concludes.

On conclusion

All green → report success with the PR URL and suggest /merge.
Any failure → identify the failing check from 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.
Pending/stuck → report what is still queued.

Notes

Read-only: this skill never pushes, merges, or re-runs jobs unless the user asks.
A common red here is commitlint: the subject started with a capitalized English word (subject-case), or the type is outside the .commitlintrc.yaml enum. Fix and re-push.