github-issue

Draft and publish reviewed GitHub issues with repository-aware gates. Resolve an explicitly named repo or the current checkout's remote, and ask when the target is ambiguous. Inspect repository issue templates and contribution guidance before drafting, run a mandatory duplicate search, gather adaptive evidence sections, validate requested or clearly implied metadata, persist markdown plus metadata in a separate git-backed workspace, and use the official GitHub MCP search_issues, issue_read, and issue_write tools with explicit auth failures or tool errors. Keep prose concise without duplicating the writer skill. Never invent identity. Use when preparing, reviewing, or filing a GitHub issue.