agentleFS
hiromailyhiromaily/go-crypto-wallet/.claude/skills/github-issue-creation/SKILL.md

github-issue-creation

Skill128 starsChanged 6 months agoMITView on GitHub

Create GitHub issues with proper task classification. Classification determines which Skills will be used when working on the issue.

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create issues with proper classification.

    line 8
  2. Distinctive:

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

    line 12
  3. Distinctive:

    Every issue must have:

    line 19
  4. Distinctive:

    Chain label: Only for cryptocurrency-specific code

    line 26
  5. Very specific:

    Test Scope label: Only when Type is test

    line 27
  6. Distinctive:

    Test scope (if applicable)

    line 37
  7. Very specific:

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

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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
    • See label-context-mapping

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

Related

  • label-context-mapping - Label → Skill/Context mapping
  • Task Classification SSOT - Label definitions
  • fix-issue command - Working on issues

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.