Menu
Use after creating PR - monitor CI pipeline, resolve failures, address review feedback, and merge when all gates pass
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when receiving UAT feedback, bug reports, user testing results, stakeholder feedback, QA findings, or any batch of issues to investigate. Investigates each item BEFORE creating issues, classifies by type and priority, creates well-formed GitHub issues with proper project board integration.
MANDATORY for all work - the project board is THE source of truth. This skill provides verification functions and gates that other skills MUST call. No work proceeds without project board compliance.
Use to spawn isolated worker processes for autonomous issue work. Uses Task tool with run_in_background for parallel execution and TaskOutput for monitoring. Pre-extracts context to minimize worker token usage.
Defines behavior protocol for spawned worker agents. Injected into worker prompts. Covers startup, progress reporting, exit conditions, and handover preparation.
Use when user requests autonomous operation across multiple issues. Orchestrates parallel workers using Task tool, monitors with TaskOutput, handles SLEEP/WAKE cycles, and works until scope is complete without user intervention.
Use for any development work - the master 13-step coding process that orchestrates all other skills, ensuring GitHub issue tracking, proper branching, TDD, code review, and CI verification
| name | ci-monitoring |
| description | Use after creating PR - monitor CI pipeline, resolve failures, address review feedback, and merge when all gates pass |
| allowed-tools | ["Bash","Read","Edit","Grep","Glob","mcp__github__*"] |
| model | opus |
Monitor CI pipeline, resolve failures, address review feedback, and merge when ready.
Core principle: CI failures AND unresolved review feedback are blockers.
Announce: "I'm monitoring CI and review feedback, and will resolve any issues before merging."
PR Created
│
▼
┌─────────────┐
│ Wait for CI │
└──────┬──────┘
│
┌───┴───┐
│ │
Green Red ──► Fix → Push → Loop back
│
▼
┌──────────────────────┐
│ Unresolved Reviews? │
└──────────┬───────────┘
┌───┴───┐
│ │
None Yes ──► For each: Evaluate → Fix/Pushback → Reply → Resolve → Push → Loop back
│
▼
┌─────────────┐
│ MERGE PR │
└─────────────┘
When both conditions met, merge immediately:
gh pr merge [PR_NUMBER] --squash --delete-branch
gh issue edit [ISSUE_NUMBER] --remove-label "status:in-review" --add-label "status:done"
Do NOT stop to report or ask. Continue to next issue.
Exception: PRs with do-not-merge label.
gh pr checks [PR_NUMBER]
gh pr checks [PR_NUMBER] --watch
gh run view [RUN_ID] --log-failedDetailed patterns: See reference/ci-failures.md
After CI green, check for unresolved threads:
gh api graphql -f query='
query($owner: String!, $repo: String!, $pr: Int!) {
repository(owner: $owner, name: $repo) {
pullRequest(number: $pr) {
reviewThreads(first: 100) {
nodes { id isResolved isOutdated comments(first: 1) { nodes { body author { login } path } } }
}
}
}
}' -f owner="[OWNER]" -f repo="[REPO]" -F pr=[PR_NUMBER]
For each unresolved thread (isResolved: false):
| Step | Action |
|---|---|
| 1 | Read and understand feedback |
| 2 | Verify: technically valid for this codebase? |
| 3 | Fix, defer (with issue), or push back with reasoning |
| 4 | Reply in thread: gh api repos/.../pulls/.../comments/[ID]/replies -f body="..." |
| 5 | Resolve: gh api graphql -f query='mutation { resolveReviewThread(...) }' |
| 6 | Push fixes, loop back to CI |
Detailed commands: See reference/review-feedback.md
Security flags from automated reviewers (Codex, CodeRabbit, etc.) should be treated seriously and verified against the codebase.
Run locally first. CI validates, doesn't discover.
pnpm lint && pnpm typecheck && pnpm test && pnpm build
If CI finds bugs you didn't find locally, your local testing was insufficient.
CI:
Review feedback:
Merge:
gh pr merge --squash --delete-branchCalled by: issue-driven-development, autonomous-orchestration
Follows: pr-creation
Uses: receiving-code-review (principles for evaluating feedback)
Completes: PR lifecycle