Agent Skills
› Tracer-Cloud/opensre
› tracking-github-work-status
tracking-github-work-status
GitHub用于查询GitHub工程状态、PR准备情况及社区跟进,将Slack请求转化为Issue。遵循只读优先原则,变更需提案并经审批后执行,支持生成状态报告与摘要。
Trigger Scenarios
查询GitHub工程状态
检查PR准备情况
总结社区跟进事项
将Slack请求转为GitHub Issue
Install
npx skills add Tracer-Cloud/opensre --skill tracking-github-work-status -g -y
SKILL.md
Frontmatter
{
"name": "tracking-github-work-status",
"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"
],
"description": "Use GitHub workflow tools to read work status, draft reports, summarize follow-ups, and execute only approved issue mutations."
}
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.
- 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.
- Report or summarize from known data. Use
generate_work_status_reportfor Slack-ready status andsummarize_community_followupsfor unanswered contributor questions or agenda items. - Propose mutations before execution. Use
propose_github_issue_mutation_from_slackonly for explicit Slack-sourced create, update, or close requests. - Execute only through approval.
execute_github_issue_mutationis the only mutating GitHub workflow tool. It is never an investigation action and must remain chat-only, approval-gated, and proposal-driven. - For ad-hoc
gh(flexible issue/PR/api ops outside this Slack proposal flow), usegithub_cli— nevershell_runwith rawgh.
Version History
-
4303874
Current 2026-09-22 10:48
技能名称重构为动名词格式(tracking-github-work-status),更新元数据并规范工具使用与工作流的文档结构。
- 719551f 2026-07-24 21:56


