comment-buglisted

# comment-bug — bug fix through a comm Same worklog-driven spine as `comment-feature`, shaped for a defect. The worklog records the **repro**, the **root cause**, the **fix**, and the **verification evidence** as durable content. Composes **`delivery-methodology`**, **`worklog`**, **`steer`**, **`review-loop`**, and **`ship`** — all sibling skills in this bundle. A bug fix is usually direct and linear; use a controlled lift only when the real fix is a foundational replacement with unsafe intermediate states. > A **`comment-prototype`** can promote INTO `comment-bug` (reusing its worklog/branch), which then adds the failing regression test a prototype skips. Reachable via the **`comment-dev`** front-door router. **Project Root.** Direct `comment-bug` uses its worklog as the Project Root. If the human or caller supplies an existing Project Root URL, preserve it and make the bug worklog a child with `Project Root: URL` near the top. Do not create a second root. **Identity.** Bug-fix comm activity follows the `worklog` route-and-identity rule. Reuse the identity carried by the working Comment.io tool/browser/connector route or a supplied Project Root token. Invoke `comment-identity` only immediately before an uncredentialed direct-REST write, then reuse that Ephemeral handle for later direct-REST worklog activity. Do not create bug worklogs as an ambient registered handle or any Botlets bot profile. **Before using a composed skill, read its full `SKILL.md`** — naming it here