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
- Distinctive: line 8
Create issues with proper classification.
- Distinctive: line 12
Load label-context-mapping skill: Use for all label → skill/context mappings
- Distinctive: line 19
Every issue must have:
- Distinctive: line 26
Chain label: Only for cryptocurrency-specific code
- Very specific: line 27
Test Scope label: Only when Type is test
- Distinctive: line 37
Test scope (if applicable)
- Very specific: line 40
Use label-context-mapping skill for label → skill/context mappings.
≈ “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.
Files
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:
- One Type label (
bug,enhancement,refactoring,documentation,security,technical-debt,test) - One Language OR Scope label (
lang:*orscope:*)
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 23. 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 workflowRelated
- label-context-mapping - Label → Skill/Context mapping
- Task Classification SSOT - Label definitions
- fix-issue command - Working on issues
In this repository62 other files it gives its agents.
- AGENTS.mdAGENTS.md
- internal/AGENTS.mdAGENTS.md
- pkg/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- internal/CLAUDE.mdCLAUDE.md
- pkg/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/agent-files.mdcCursor rule
- .cursor/rules/apps/bun.mdcCursor rule
- .cursor/rules/apps/eth-contracts.mdcCursor rule
- .cursor/rules/apps/xrp-server.mdcCursor rule
- .cursor/rules/database/atlas-hcl.mdcCursor rule
- .cursor/rules/database/sqlc.mdcCursor rule
- .cursor/rules/documentation-language.mdcCursor rule
- .cursor/rules/general.mdcCursor rule
- .cursor/rules/github-actions.mdcCursor rule
- .cursor/rules/go/conventions.mdcCursor rule
- .cursor/rules/go/di.mdcCursor rule
- .cursor/rules/go/go-path.mdcCursor rule
- .cursor/rules/go/go-test.mdcCursor rule
- .cursor/rules/internal/application-layer.mdcCursor rule
- .cursor/rules/internal/btc-shared.mdcCursor rule
- .cursor/rules/internal/clean-architecture.mdcCursor rule
- .cursor/rules/internal/cli-structure.mdcCursor rule
- .cursor/rules/internal/domain-layer.mdcCursor rule
- .cursor/rules/internal/dto.mdcCursor rule
- .cursor/rules/internal/infrastructure-layer.mdcCursor rule
- .cursor/rules/internal/interface-adapters-layer.mdcCursor rule
- .cursor/rules/internal/internal-interface.mdcCursor rule
- .cursor/rules/internal/mockery.mdcCursor rule
- .cursor/rules/internal/repository.mdcCursor rule
- .cursor/rules/internal/usecase.mdcCursor rule
- .cursor/rules/proto.mdcCursor rule
- .cursor/rules/README.mdCursor rule
- .cursor/rules/security.mdcCursor rule
- .cursor/rules/shell-script.mdcCursor rule
- .cursor/rules/ssot.mdcCursor rule
- .cursor/rules/task-context-loading.mdcCursor rule
- .cursor/rules/typescript.mdcCursor rule
- .cursor/rules/yaml.mdcCursor rule
- llms.txtllms.txt
- bch-developmentSkill
- btc-terminologySkill
- db-migrationSkill
- devopsSkill
- docs-ssotSkill
- docs-updateSkill
- fix-pr-reviewSkill
- git-workflowSkill
- go-developmentSkill
- knowledge-gapSkill
- label-context-mappingSkill
- makefile-updateSkill
- mockerySkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
- shell-scriptsSkill
- solidity-developmentSkill
- The first 60 shown.
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.

