Agent Skills
› Tracer-Cloud/opensre
› github-workflow
github-workflow
GitHub用于查询GitHub工程状态、PR准备情况及社区跟进,或将Slack请求转化为Issue。包含只读报告生成与需审批的Issue变更执行流程。
Trigger Scenarios
询问GitHub工程状态或PR准备情况
需要生成工作进度报告
总结社区未回答问题
将Slack请求转为GitHub Issue
Install
npx skills add Tracer-Cloud/opensre --skill github-workflow -g -y
SKILL.md
Frontmatter
{
"name": "github-workflow",
"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
- 719551f Current 2026-07-24 21:56


