Let bugfix start from a ticket key - #20
Merged
Merged
Conversation
`/colormath:bugfix CM-00012` now reads the ticket over MCP instead of needing the report pasted in. Prose, a stack trace and a path to a report file behave exactly as before — the skill branches on which of the three shapes it was handed. A bug is usually a ticket by the time somebody fixes it, and `bugfix` was the only key-shaped skill that could not take one: `refine-ticket`, `implement-ticket`, `refine-initiative` and `plan-initiative` all do. The workaround was copying the description out of the tracker, which silently drops the comment thread — where a filed bug's actual reproduction usually ends up. So the skill is told to read every comment, and told that a numbered ticket is still evidence rather than a specification. It also closes the loop, the way implement-ticket does: a run that started from a ticket comments the outcome back on it and leaves the ticket's own fields and lane alone. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NFTx8sFMcQPxn2RH8z4jDG
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
/colormath:bugfix CM-00012now reads the ticket over MCP — description, type,every comment, and the plans if it was groomed — instead of needing the report
pasted in. Prose, a stack trace and a path to a report file all behave exactly
as before; the skill branches on which of the three shapes it was handed.
Why
A bug is usually a ticket by the time somebody fixes it, and
bugfixwas theodd one out:
refine-ticket,implement-ticket,refine-initiativeandplan-initiativeall take a key. The only way to handbugfixa filed bug wasto copy the description out of the tracker — which silently drops the comment
thread, and that is where a filed bug's actual reproduction usually ends up.
So reading the thread is the point rather than a side effect: the skill is told
to read every comment, because the environment, the repro somebody finally
landed on, and the "it also happens when…" typically live there and not in the
description. What it must not do is treat a numbered ticket as more
authoritative than a pasted paragraph — step 1 ("find what's missing") applies
unchanged either way, and the text says so.
What changed
argument-hintnames both forms.allowed-toolsgainsmcp__abacus__get_ticket,list_boards,list_ticketsandadd_comment— the same read setrefine-ticketcarries,plus the comment write. A consumer with no abacus MCP server configured is
unaffected: the pasted-report path never touches those tools.
with the title-fragment fallback (
list_boards→list_tickets, confirmwhich one you landed on) worded as
refine-ticketwords it.add_comments the outcome — PR link, merged or held, the cause, what itdeliberately left alone — matching
implement-ticket. It leaves the ticket'sown fields and lane alone; the description is what was reported, the comment
is what happened, and whether a bug is done is the filer's call.
Release
MINOR per LIFECYCLE.md — a new input shape with the old ones
unchanged. Notes are under
## Unreleased; no version stamped.Markdown only: no gate, script, action, input or vendored file is touched, so
the self-hosted suite against
example/is unaffected.🤖 Generated with Claude Code
https://claude.ai/code/session_01NFTx8sFMcQPxn2RH8z4jDG