← ClaudeAtlas

niceticketlisted

Write a short, well-formatted Jira bug ticket - a Title Case title and a body that says what breaks, for whom and how often, with only the sections the facts support (steps, expected vs actual, cause, fix, acceptance criteria), code links as permalinks. From a bug report, a Sentry issue, logs or an investigation's facts. Drafts only; /jira creates it.
sgtlaugh/skills · ★ 2 · Code & Development · score 76
Install: claude install-skill sgtlaugh/skills
# /niceticket - Write a Jira Ticket Turn what is known about a bug into a ticket a teammate, a PM or QA can act on in a minute. The counterpart of `/nicepr`: that one describes a change, this one describes a problem. ## Usage ``` /niceticket <what you have> # a pasted report, a Sentry issue URL or ID, log lines, a Slack thread /niceticket # from the conversation so far ``` It drafts only: it reads (`gh api` GETs, git history, `/sentry`) and writes nothing anywhere. Create the ticket with `/jira` once you have read it; creating or editing a ticket, or any `gh api` call with `-X`, `--method`, `-f` or `-F`, from here is WRONG. A caller (a script that already investigated) may pass the facts in the prompt: the cause, its evidence, the repo and the commit the code was read at, the PR. Then use only those facts, fetch nothing, and say nothing they don't support. ## Step 1 - Gather the facts - A Sentry issue: invoke `/sentry` for its title, event count, first and last seen, and the stack frames that point at code. - Logs or a pasted report: take the symptom, when it happens, how often, and who sees it. - Code: find the lines that matter and the commit they were read at (`git rev-parse <remote>/<default branch>` on a fetched remote, or the commit the caller gave). Before linking it, confirm the commit is on the remote: `gh api repos/<org>/<repo>/commits/<sha> --jq .sha` prints it, or `git branch -r --contains <sha>` lists a remote branch. A co