github-issue-creation

Create well-structured GitHub issues using the gh CLI tool. Use when the user wants to create a GitHub issue, track features, bugs, refactoring tasks, or technical debt for the go-crypto-wallet repository.

⭐98stars🔀27forks📁View on GitHub🕐Updated Jan 8, 2026⬇️1downloads

When & Why to Use This Skill

This Claude skill automates the creation of well-structured GitHub issues using the GitHub CLI (gh). It streamlines the development lifecycle by enforcing standardized task classification through mandatory labels, ensuring that bugs, features, and technical debt are documented with clear descriptions and acceptance criteria for efficient team collaboration and agentic workflows.

Use Cases

  • Standardized Bug Reporting: Automatically generate detailed bug reports with required 'bug' and 'scope' labels to ensure developers have all necessary context and metadata.
  • Feature Request Management: Create structured enhancement issues that include clear acceptance criteria and language-specific labels for better roadmap tracking and prioritization.
  • Technical Debt Documentation: Quickly log refactoring tasks or security vulnerabilities using predefined templates to maintain repository health and code quality.
  • Agentic Workflow Integration: Utilize specific labels during issue creation to automatically determine which specialized AI skills or contexts should be loaded for subsequent task execution.
namegithub-issue-creation
descriptionCreate GitHub issues with proper task classification. Classification determines which Skills will be used when working on the issue.

GitHub Issue Creation

Create issues with proper classification. Labels determine which Skills are used.

Prerequisites

  • Load label-context-mapping skill: Use for all label → skill/context mappings

Label Selection Rules

Required Labels

Every issue must have:

  1. One Type label (bug, enhancement, refactoring, documentation, security, technical-debt, test)
  2. One Language OR Scope label (lang:* or scope:*)

Optional Labels

  • Chain label: Only for cryptocurrency-specific code
  • Test Scope label: Only when Type is test

Issue Creation Process

1. Classify Task

From user request, determine:

  • Type (bug, enhancement, refactoring, documentation, security, technical-debt, test)
  • Language OR Scope
  • Test scope (if applicable)
  • Chain (if applicable)

Use label-context-mapping skill for label → skill/context mappings.

2. Create Proposal

## Proposed Issue

**Title**: [Clear title - 50-72 chars]

**Labels**: [type], [lang/scope], [test scope if applicable], [chain if applicable]

**Skills**: [git-workflow] + [skill based on label-context-mapping]

**Body**:
## Description
[What needs to be done]

## Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2

3. Create Issue (After Approval)

gh issue create \
  --title "Title" \
  --body "Body" \
  --label "type,lang/scope,chain"

Quick Reference

Required: [Type] + [Language OR Scope]
Optional: [Test Scope] + [Chain]

→ Labels determine Skills (see label-context-mapping)
→ Skills determine workflow