tracking-github-work-status
Use GitHub workflow tools to read work status, draft reports, summarize follow-ups, and execute only approved issue mutations.
来源信息
- 仓库
- tracer-cloud/opensre
- 最近来源活动
- 2026年10月4日 10:07
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 11,970
- 分支
- 1,759
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
文件资源管理器
6 个文件正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- tracking-github-work-status
- description
- Use GitHub workflow tools to read work status, draft reports, summarize follow-ups, and execute only approved issue mutations.
- tools
- ["list_github_work_items","summarize_github_pr_status","list_github_security_alerts","generate_work_status_report","summarize_community_followups","propose_github_issue_mutation_from_slack","execute_github_issue_mutation"]
# GitHub Workflow
Use this workflow when the user asks about GitHub engineering status, PR readiness,
community follow-ups, or turning an explicit Slack request into a GitHub issue.
1. Read before reporting. Use the read-only GitHub tools first, and treat missing
or failed reads as incomplete status rather than proof that there are no
blockers.
2. Report or summarize from known data. Use `generate_work_status_report` for
Slack-ready status and `summarize_community_followups` for unanswered
contributor questions or agenda items.
3. Propose mutations before execution. Use
`propose_github_issue_mutation_from_slack` only for explicit Slack-sourced
create, update, or close requests.
4. Execute only through approval. `execute_github_issue_mutation` is the only
mutating GitHub workflow tool. It is never an investigation action and must
remain chat-only, approval-gated, and proposal-driven.
5. For ad-hoc `gh` (flexible issue/PR/api ops outside this Slack proposal flow),
use `github_cli` — never `shell_run` with raw `gh`.
在 GitHub 查看