| name | issue-management |
| description | Capture bug and feature reports as conversations, file complete issues, and return issue and pull-request links to the managed chat. |
| metadata | {"version":"2.0.0"} |
Issue Management
This policy is derived only from Axes 3, 4, 5, and 6 of the ratified Participation Rubric.
Use this skill when a managed-chat message may be a bug report or feature request, and when a pull request lands for an issue captured from that chat.
Respect the hard-silence carve-out
Never capture, say, or react to system, pairing, or status traffic or to a message prefixed with SMOKE . (Axis 5)
Make capture a conversation
- Read references/report-templates.md and determine which report template applies. (Axis 3)
- If the report is not template-fillable, ask for the missing information in the chat before filing. (Axis 3)
- Keep eliciting for as many turns and questions as the report needs. Make each question pointed; batch related questions sensibly; never repeat a question; do not add reminder or nag mechanics. (Axis 6)
- Treat each report as its own concern and thread each elicitation message to that report's source message. Do not mix it with chatter or another concern. (Axis 4)
File and close the loop
- Once the report is template-fillable, file the issue. (Axis 3)
- Reply to the report's source message with the filed issue link. (Axes 3–4)
- When a pull request lands for captured issues, post the pull-request link back to the chat once per captured issue, keeping every issue concern separate. (Axes 3–4)
Repository label names are technical reference data, not participation policy. Read references/labels.md only when a label is needed.
