---

name: github-issue description: Create GitHub issues with templates, diagrams for proposals, and context from linked issues/PRs

GitHub Issue Creation Skill

Workflow

1. Gather Context from Linked Issues/PRs

If the user provides GitHub issue or PR links:

• Use mcp__github__issue_read with method: "get" to fetch issue details
• Use mcp__github__pull_request_read with method: "get" to fetch PR details
• Review the linked content and incorporate relevant context into the new issue

2. Discover Issue Templates

Step 1: Check target repository Use mcp__github__get_file_contents to check for templates:

Copyowner: {repo_owner}
repo: {repo_name}
path: .github/ISSUE_TEMPLATE/

Step 2: If no templates found, check org's .github repository

Copyowner: {repo_owner}
repo: .github
path: .github/ISSUE_TEMPLATE/

Step 3: Select appropriate template Analyze the user's request and auto-select the most appropriate template:

• Bug reports: templates containing "bug" in name
• Feature requests: templates containing "feature" or "request" or "proposal" or "rfc"

If multiple templates exist and the best match is unclear, briefly list options and ask the user.

3. Create Proposal Diagrams

For issues that propose changes to architecture, workflows, or systems, create a unified Mermaid diagram showing both current and proposed states.

Diagram Guidelines:

• Draw a single unified diagram containing both current and new states
• Elements that will be removed: style with red (fill:#ffcccc,stroke:#ff0000)
• Elements that are new/added: style with green (fill:#ccffcc,stroke:#00ff00)
• Elements that remain unchanged: use default styling

Example:

Copyflowchart LR
    A[Client] --> B[Old API Gateway]
    A --> C[New API Gateway]
    B --> D[Service]
    C --> D
    C --> E[New Cache Layer]

    style B fill:#ffcccc,stroke:#ff0000
    style C fill:#ccffcc,stroke:#00ff00
    style E fill:#ccffcc,stroke:#00ff00

Legend: Always include a legend below the diagram:

• Red = Current state (to be removed)
• Green = Proposed state (to be added)
• Default = Unchanged

4. Draft and Review (REQUIRED)

IMPORTANT: Always present the complete draft issue to the user for review before creating it.

Present the draft in this format:

Copy## Draft Issue Preview

**Repository:** {owner}/{repo}
**Title:** {title}
**Labels:** {labels}

---
{full issue body}
---

Would you like me to create this issue, or would you like to make any changes?

Wait for explicit user confirmation before proceeding. Accept modifications if requested.

5. Create the Issue

Only after user confirmation, use mcp__github__issue_write with:

Copymethod: "create"
owner: {repo_owner}
repo: {repo_name}
title: {issue_title}
body: {issue_body}
labels: {from_template_if_available}

Fallback Body Structure (when no template available): If using a template, follow its structure. Otherwise use this format with no headings:

Copy[Brief description of the issue/proposal]

[Any relevant context from linked issues/PRs]

[Description of proposed changes, if applicable]

[Mermaid diagram if this is a proposal]

**Legend:**
- Red = Current state (to be removed)
- Green = Proposed state (to be added)

[Any other relevant information]