菜单
Triage a bug report into an actionable GitHub issue with severity, reproduction steps, and assignment. Use when a bug is reported, when error logs need investigation, or when asked to file/triage an issue.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Close implementation loops with target-bound independent evidence and a portable proof receipt. Use when an agent changes a real system and must earn a completion claim that survives the session.
First fixture skill for skdd add tests. Use when testing drop installation.
Second fixture skill for skdd add tests. Use when testing multi-skill drops.
Safely backfill historical data for a pipeline stage — scope the date range, run a dry-run, execute in chunks to avoid overwhelming the database, and verify row counts after each chunk. Use when historical data is missing, when a pipeline stage is added retroactively, or when asked to "backfill the {stage} table from {start_date}".
Add or extend data validation checks in the pipeline when data quality issues are detected — null-percentage thresholds, value ranges, referential integrity, and row-count sanity checks. Use when a pipeline breaks on bad data, when onboarding a new dataset, or when asked to "add a quality check for {column}".
Onboard a new raw dataset into the data platform — sniff the schema, generate a profiling notebook, create the ingestion job, and add an entry to the data dictionary. Use when adding a new data source, when a partner delivers a new CSV/Parquet drop, or when asked to "onboard the {name} dataset".
| name | bug-triage |
| description | Triage a bug report into an actionable GitHub issue with severity, reproduction steps, and assignment. Use when a bug is reported, when error logs need investigation, or when asked to file/triage an issue. |
| metadata | {"forged-by":"claude-agent","forged-from":"session-2026-02-20","forged-reason":"Forked from ops-toolkit — adapted for this project's labeling and priority scheme","fork-of":"ops-toolkit/bug-triage","usage-count":"6","last-used":"2026-02-25"} |
Convert a bug report (user message, error log, Sentry alert) into a well-structured GitHub issue.
Reproduce or verify
Classify severity
| Severity | Criteria | Label |
|---|---|---|
| P0 | Data loss, security, or full outage | severity:critical |
| P1 | Major feature broken, no workaround | severity:high |
| P2 | Feature broken, workaround exists | severity:medium |
| P3 | Minor annoyance, cosmetic | severity:low |
Identify the component
area:frontend, area:backend, etc.Write the GitHub issue
## Bug: [one-line description]
**Severity:** P[0-3]
**Environment:** [production/staging/local]
**Reporter:** [name or "internal"]
### What happened
[Clear description of the bug]
### Expected behavior
[What should have happened]
### Reproduction steps
1. ...
2. ...
3. ...
### Evidence
[Error logs, screenshots, Sentry link]
### Suspected cause
[If you have a hypothesis, state it]
File the issue
gh issue create --title "Bug: [description]" --body "[body]" --label "bug,severity:[level],area:[component]"
Assign if obvious
Bug:severity: and area: labelscripts/notify-critical.sh)enhancement and move to backlog.