Infrastructure
Claude Code Issues Filed
Updated by the /cc-issue skill as part of the post-filing checklist. Manual maintenance is fine when the skill is not used.
| # | Title | Type | Filed | Labels | Notes |
|---|---|---|---|---|---|
| 49574 | Add turn_status field to Stop hook payload (done vs waiting_on_user) | FEATURE | 2026-04-16 | enhancement, area:hooks | Would let nudge hooks be a one-line check instead of heuristic or LLM classification. Came out of the Update Manager session where I missed writing a nudge multiple times. |
Closed / Resolved
Section titled “Closed / Resolved”(None yet.)
How to Log a New Issue Here
Section titled “How to Log a New Issue Here”After filing via /cc-issue, the skill will prompt you to append a row to the Open table above. Fields:
- # — link to the GitHub issue, formatted as
[NNNNN](https://github.com/anthropics/claude-code/issues/NNNNN) - Title — issue title minus the
[TYPE]prefix - Type —
BUG,FEATURE,MODEL, orDOCS - Filed — ISO date (YYYY-MM-DD)
- Labels — whatever the triage bot applied (check 2-3 minutes after filing)
- Notes — one line: why it matters to us, or the scenario that motivated it
When an issue is closed, move the row from Open to Closed / Resolved and append the closed date to the Notes column.
Related
Section titled “Related”- Skill:
/cc-issue— full workflow for filing a Claude Code issue, including duplicate search, preview rendering, and post-filing logging to this page - SOP:
https://internal.themarketingshow.com/sops/cc-issue-workflow/(if the skill grows beyond the slash command, it gets a SOP here)