Create a GitHub issue from recent changes, commit only relevant diffs on a short-lived task branch, push that branch, and open a PR into master that will close the issue on merge. Use when the user says "make closed issue", "close issue", or wants to create a tracked, already-resolved GitHub issue for completed work.
Create a GitHub issue from recent changes, commit only relevant diffs on a short-lived task branch, push that branch, and open a PR into master that will close the issue on merge. Use when the user says "make closed issue", "close issue", or wants to create a tracked, already-resolved GitHub issue for completed work.
Make Closed Issue
Creates a GitHub issue, commits relevant changes on a review branch, pushes the branch, and opens a PR into master that closes the issue when merged.
Inputs
What changed and why (from prior conversation context)
Uncommitted or staged git changes in the working tree
Workflow
1. Determine label(s)
Ask the user using AskQuestion (multi-select):
Option
When
bug
Bug fix
enhancement
New feature
bug + enhancement
New feature that also fixes a bug
documentation
README, AGENTS.md, docs-only changes
2. Ensure branch workflow is reviewable
If already on a short-lived task branch such as feature/*, fix/*, docs/*, or chore/*, stay on it.
If on master, create a task branch before staging or committing.
Do not commit the work directly on master when PR review bots or human review are expected.
Suggested naming:
feature/short-slug
fix/short-slug
docs/short-slug
chore/short-slug
Example:
git switch -c fix/replies-cache-reset
3. Review diffs for relevance
git status
git diff
git diff --cached
Identify which files relate to the work done in this conversation. Only relevant changes get committed. Unrelated files must be excluded from staging.
Important: git add -p and git add -i are not available (interactive mode unsupported). If a file has mixed relevant/irrelevant changes, include the entire file and note the caveat to the user.
4. Generate issue title and description
From the conversation context:
Title: Short, present-tense, describes the problem (not the solution). Use backticks for hooks, stores, commands, or literal strings when helpful.
Description: 2-3 sentences about the problem. Use backticks for code references or literal names. Write as if the issue hasn't been fixed yet.
