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 언어
- 영어
- 스타
- 12,723
- 포크
- 1,868
설치 방법
기본적으로 소스를 먼저 확인하는 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에서 보기