菜单
Capture bug and feature reports as conversations, file complete issues, and return issue and pull-request links to the managed chat.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Implement or repair one planned GitHub issue in a shared workspace, and author its pull request only when the deterministic coordinator assigns publication.
Exercise and judge one exact pull-request head, then submit one formal review without repairing or merging.
Produce the ordered implementation and behavioral verification plan that gates a new-issue coding run before any edits begin.
Verify that a code change actually does what it's supposed to by exercising it end-to-end and observing behavior — drive the affected flow, not just tests or typecheck. Run before committing nontrivial changes; bootstraps this repo's project verify skill if none exists yet. Don't invoke it on a diff that only touches tests, docs, or other code with no runtime surface to drive (a change to product source always has one) — there's nothing to observe.
Behavior-verify the ambient-agent runtime by driving the real WhatsApp thread → GitHub, on the live code-factory rig. Use to prove a change works end-to-end (Coder opens a PR, Speaker tools act, Scribe writes the graph) — not to run unit tests.
Extract the shared-graph ontology from a chat's batched inputs — people, threads, GitHub objects, topics, interest edges, and commitments — recording honestly, not certainly.
| 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"} |
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.
Never capture, say, or react to system, pairing, or status traffic or to a message prefixed with SMOKE . (Axis 5)
Repository label names are technical reference data, not participation policy. Read references/labels.md only when a label is needed.
