name: github-issue-creation description: Create 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.

SSOT Reference: See Task Classification for the authoritative definition of all labels and mappings.

Label Categories

Type Labels (Required)

Language Labels (For Code Tasks)

Scope Labels (For Non-Code Tasks)

Chain Labels (For Cryptocurrency Tasks)

Test Scope Labels (When Type is test)

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

Label → Skill Mapping Examples

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)

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]

**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
→ Skills determine workflow

Related Documents

• Task Classification SSOT - Authoritative label definitions
• Task Context Loading - Context loading rules