Menu
Implement issue, review PR, and verify CI — runs issue-implement, pr-review-loop, and pr-check-loop sequentially
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
Start the development server in background mode
Start dev server and interact with the platform via agent-browser. Use when user asks to browse, test, or demo the platform UI, connect services, or perform any browser-based interaction with the local dev environment.
Reset turbo environment (clean node_modules, reinstall, sync DB)
Check if a PR, commit, or tag has been deployed to production
Query, investigate, and manage Sentry issues for debugging and incident response
Create or update a PR and hand it off to a coding agent worker via load balancing. Removes pending label if present, then assigns a worker.
| name | issue-action |
| description | Implement issue, review PR, and verify CI — runs issue-implement, pr-review-loop, and pr-check-loop sequentially |
You are an issue-to-PR specialist. Your role is to implement a GitHub issue, then shepherd the resulting PR through code review and CI by running three skills in sequence.
Your args are: $ARGUMENTS
Args are passed through to the issue-implement skill (typically empty — it detects the issue from conversation context).
Run these three skills sequentially. Each skill must complete before starting the next.
invoke skill /issue-implement
Implement the issue following the approved plan, create a feature branch, write code and tests, and create a Pull Request.
If implementation exits with "pending" label (blocked, needs clarification): Stop here. Do NOT proceed to Step 2.
Extract the PR number from the output for the next steps.
invoke skill /pr-review-loop <PR_NUMBER>
Iteratively review the PR, post findings, fix P0/P1 issues, and repeat until LGTM or max iterations.
If review ends with "Changes Requested (max iterations)": Stop here. Add "pending" label to the issue and report that manual intervention is needed. Do NOT proceed to Step 3.
invoke skill /pr-check-loop <PR_NUMBER>
Monitor CI pipeline, auto-fix lint/format issues, and loop until all checks pass.
If checks end with "Manual Fix Required" or "Timeout": Add "pending" label to the issue and report the failure.
Post a comment to the issue:
gh issue comment {issue-id} --body "Work completed. PR created: {pr-url}
Code review passed and all CI checks passing."
Add "pending" label to the issue and exit:
gh issue edit {issue-id} --add-label pending
After the workflow completes (or stops early), display:
Issue Action Complete
Issue: #{issue-id} - {title}
Implementation: <PR Created / Blocked>
Review: <LGTM / Changes Requested / Skipped>
CI: <All Passed / Failed / Skipped>
PR: {pr-url or N/A}
If any step was skipped due to a prior failure, show "Skipped" for that step.