메뉴
Orient planner work that references GitHub-tracked issues, pull requests, comments, or repositories through Bluex synced state instead of direct GitHub mutation.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Operate Bluex Next in production: create GitHub issues, inspect Bluex API state, monitor ubuntu-blue over SSH, and query the live production PostgreSQL database. Use when the user asks to operate, monitor, debug, triage, or create work for bluex-next/Bluex.
Implement Bluex repository work as basic.implementer by inspecting issue/work/PR context, changing the prepared workspace, registering or updating pull requests, marking implementation ready, completing work, or blocking work through the Bluex CLI. Use for repo_change, review feedback, CI failure, and conflict work.
Triage and orient GitHub repository, pull request, and issue work through the connected GitHub app. Use when the user asks for general GitHub help, wants PR or issue summaries, or needs repository context before choosing a more specific GitHub workflow.
Integrate Bluex approved pull request work as basic.integrator by inspecting issue/PR context, optionally refreshing tracker state, updating PR and issue state, completing work, or blocking integration through the Bluex CLI. Use for merge-ready and integration work.
Plan Bluex work as basic.planner by turning PRDs, broad requests, and product intent into explicit Bluex issues with routing signals. Use when acting as the Bluex planning agent and needing to inspect issues, create planned issues, comment, complete work, or block work through the Bluex CLI.
Implement Bluex repository work as ui.implementer by inspecting issue/work/PR context, changing the prepared workspace, registering or updating pull requests, marking implementation ready, completing work, or blocking work through the Bluex CLI. Use for repo_change, review feedback, CI failure, and conflict work.
| name | github |
| description | Orient planner work that references GitHub-tracked issues, pull requests, comments, or repositories through Bluex synced state instead of direct GitHub mutation. |
The planner does not own GitHub repository mutations, PR creation, review follow-up, CI debugging, or publishing changes. For planning work, GitHub is tracker context that has already been synced into Bluex issue, comment, pull request, and signal state.
issues.get_execution_context and issues.get for issue and tracker metadata.planning.create_follow_up_work, planned_issues.create_batch, and issues.update_signals to represent the plan in Bluex.comments.create_issue_handoff to publish the planning decision trace.comments.create_issue_handoff fails, block with the exact failure instead of posting through the GitHub app, github.issues.comment, or raw gh; unsynced GitHub issue comments can be imported as human intent and create duplicate work.gh unless a required public fact is absent from Bluex state and no registered tool exposes it; if that happens, explain the missing field in the decision trace.When GitHub context affects the plan, write it into public Bluex state:
target.repotarget.arearouting.kind, routing.worker, and harness when runner choice mattersdependsOnKeysrequiredOutputsreview.required, merge.policy