rewrite-gh-issuelisted

# Goal Improve an existing GitHub issue by gathering the current issue content, investigating the local codebase for relevant context, asking focused follow-up questions to fill in missing details, and rewriting the issue in a clearer, more actionable structure. If a matching GitHub issue template exists in the workspace, use its style and structure. Always ask the user for final confirmation before updating the issue title and body. # Inputs Expected input from the user: - a GitHub issue number - optional intent, such as: - make this issue more actionable - rewrite this bug report - turn this into a proper feature request - align this with our issue template - clean up and update issue 123 # Tools and environment assumptions This skill assumes: - the current working directory is a local clone of the target GitHub repository - the GitHub CLI `gh` is installed and authenticated - the current git remote points to the repository containing the issue - the workspace may contain issue templates under common GitHub locations Common template locations to inspect: - `.github/ISSUE_TEMPLATE/` - `.github/issue_template/` - `docs/` - repository root for issue form or markdown templates # High-level behavior Follow this approach: 1. Validate the environment. 2. Fetch the issue by number using the GitHub CLI. 3. Inspect the current issue title, body, labels, and metadata. 4. Explore the codebase, docs, tests, and configuration related to the issue. 5. Ask the user ta