← ClaudeAtlas

add-issuelisted

Add one issue to the repo's issue tracker from a short request, and ship it. Use when the user asks to open, add or create an issue, or starts the request with "add idea".
praisethebit/skills · ★ 1 · AI & Automation · score 77
Install: claude install-skill praisethebit/skills
Add one issue for: $ARGUMENTS Each step ends on its completion criterion. 1. **Read.** Read the repo's issue tracker doc. Run `~/.claude/bin/next-issue --claim` to get the next free number. Why: `--claim` keeps a parallel session from getting the same number. If you cannot tell what the issue is about, ask the user one question. Done when you have the next free number and the subject. 2. **Look.** Use a maximum of 8 searches or reads in the code. When a review finding is the source, name the class of the gap and list all members of the class. Do not name only the one case that the review found. Done when you can name the files that the issue touches, not the fix. 3. **Write.** Write the issue in the tracker's format, with a maximum of 6 acceptance criteria. When the issue has acceptance criteria, end each criterion with its proof, for example `(proof: unit test)`, and add an `## Out of scope` section after the criteria ("None." is valid). An idea card needs neither. Set `stage` by the stage rule below. For "add idea: X", write the idea as the title and one line of text. When the search cap ends before you find all members of the class, write the missing members as an open question. When a review finding is the source, put the class and all known members in the issue. In a repo where the `AGENTS.md` has the line ``Behavior spec: `docs/spec/`.``, write a behavior criterion and `behavior_spec` (a file named after a durable capability of the product, not after this work) only w