AGENT SKILL

github

Orient planner work that references GitHub-tracked issues, pull requests, comments, or repositories through Bluex synced state instead of direct GitHub mutation.

License 许可
MIT
所属仓库
getbluex/bluex
最近更新
2026-06-29
Stars
★ 3
Forks
0

01 前言 Front Matter

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.

02 资源文件 3

03 SKILL.md 正文

GitHub Context For Planner

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.

Use This Skill For

  • Interpreting a GitHub-backed Bluex issue, PR, comment, or repository reference during planning.
  • Deciding whether an issue should become a repo-change, review, merge, or product-planning work item.
  • Writing acceptance criteria, completion contracts, routing signals, dependencies, and required outputs for future agents.

Operating Boundary

  • Use issues.get_execution_context and issues.get for issue and tracker metadata.
  • Use the recent comments embedded in the prompt context for GitHub issue discussion history.
  • Use planning.create_follow_up_work, planned_issues.create_batch, and issues.update_signals to represent the plan in Bluex.
  • Use comments.create_issue_handoff to publish the planning decision trace.
  • If 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.
  • Do not create GitHub issues or pull requests directly.
  • Do not inspect GitHub through raw 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.
  • Do not assume external GitHub plugin specialist skills exist in the materialized workspace.

Planning Output

When GitHub context affects the plan, write it into public Bluex state:

  • Target repository: target.repo
  • Expected changed area: target.area
  • Routing: routing.kind, routing.worker, and harness when runner choice matters
  • Dependencies: dependsOnKeys
  • Completion evidence: requiredOutputs
  • Review and merge policy: review.required, merge.policy

04 同仓库更多 Skills