github-issue-draftinglisted

# GitHub issue drafting A short note ("fix the retry backoff", "SSM params", "the CLI hangs on empty input") carries enough for whoever wrote it and too little for anyone else, including the same person in six months. The job is an issue a reader can act on without asking what was meant, with every claim about the code checked against the code. ## Process 1. **Get the note.** Use the text passed in as the skill argument. Ask the user for it if none arrived. A note can come from anywhere (a to-do app, a chat message, a `TODO` comment, a stack trace, a support thread) and the source changes nothing about the drafting. 2. **Work out which repository this belongs to, and how it files issues.** `gh repo view` names the repository behind the working directory. Confirm with the user where the working directory is ambiguous or where the issue belongs somewhere else. Then read how this project already works: - `.github/ISSUE_TEMPLATE/` and `CONTRIBUTING.md`, if present. **A repository's own template wins over the structure in this skill.** Fill in that template and follow its wording. - `gh issue list --limit 10` and one or two full issues (`gh issue view <n>`) for the house register, the section headings in use, and how long a typical issue runs. 3. **Investigate before drafting.** See [Ground the draft in the repository](#ground-the-draft-in-the-repository). 4. **Decide whether it is one issue or several.** See [One note is often more than on