label-context-mapping
Maps GitHub labels to Skills and Context documents. Use when creating issues (github-issue-creation) or working on issues (fix-issue command).
Best use case
label-context-mapping is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Maps GitHub labels to Skills and Context documents. Use when creating issues (github-issue-creation) or working on issues (fix-issue command).
Teams using label-context-mapping should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/label-context-mapping/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How label-context-mapping Compares
| Feature / Agent | label-context-mapping | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Maps GitHub labels to Skills and Context documents. Use when creating issues (github-issue-creation) or working on issues (fix-issue command).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Label → Context Mapping Central mapping from GitHub labels to Skills and Context documents. **SSOT**: This skill defines the operational mappings. Label definitions are in [Task Classification](../../../docs/guidelines/task-classification.md). ## When to Use - **Creating issues**: Determine which labels to apply - **Working on issues**: Determine which skills and contexts to load ## Label Categories ### Type Labels → Context Documents | Label | Context Document | | ---------------- | ------------------------------------- | | `bug` | `docs/ai/task-contexts/bug-fix.md` | | `enhancement` | `docs/ai/task-contexts/feature-add.md` | | `refactoring` | `docs/ai/task-contexts/refactoring.md` | | `documentation` | `docs/ai/task-contexts/documentation.md` | | `security` | `docs/ai/task-contexts/security.md` | | `technical-debt` | `docs/ai/task-contexts/refactoring.md` | | `test` | `docs/ai/task-contexts/test.md` | ### Language Labels → Skills | Label | Skill | Verification | | ----------------- | ------------------------ | ----------------------------------------------------------------------------------- | | `lang:go` | `go-development` | `make go-lint && make tidy && make check-build && make go-test` | | `lang:typescript` | `typescript-development` | See skill for app-specific commands (Bun for xrpl-grpc-server, npm for eth-contracts) | | `lang:solidity` | `solidity-development` | `truffle compile && truffle test` | ### Scope Labels → Skills | Label | Skill | Verification | | ---------------- | ----------------------------------- | ------------------------------------------------ | | `scope:docs` | `docs-update` | Markdown formatting | | `scope:devops` | `devops` | `yamllint`, workflow test | | `scope:scripts` | `shell-scripts` | `make shfmt` | | `scope:makefile` | `makefile-update` | `make mk-lint` | | `scope:db` | `db-migration` (+ `go-development`) | `make atlas-fmt && make atlas-lint && make sqlc` | | `scope:config` | - | Syntax validation | | `scope:proto` | - | `make proto` | ### Chain Labels → Context Documents | Label | Context Documents | | ------------- | ------------------------------------------------------------------- | | `chain:btc` | `docs/ai/task-contexts/chain-specific.md`, `docs/chains/btc/README.md` | | `chain:bch` | `docs/ai/task-contexts/chain-specific.md`, `docs/chains/bch/README.md` | | `chain:eth` | `docs/ai/task-contexts/chain-specific.md`, `docs/chains/eth/README.md` | | `chain:erc20` | `docs/ai/task-contexts/chain-specific.md`, `docs/chains/eth/README.md` | | `chain:xrp` | `docs/ai/task-contexts/chain-specific.md`, `docs/chains/xrp/README.md` | | `chain:all` | `docs/ai/task-contexts/chain-specific.md` | ### Test Scope Labels → Verification | Label | Verification | | ------------------ | -------------------------------------- | | `unit-test` | `make go-test` | | `integration-test` | `make go-test-integration` | | `e2e-test` | `make btc-e2e-*` or chain-specific E2E | ## Loading Procedure ### From Issue Labels ``` 1. Parse issue labels 2. Load contexts: - Type label → Context document - Chain label → Chain context (if present) 3. Load skills: - Always: git-workflow - Lang/Scope label → Development skill 4. Apply verification commands from skill ``` ### Mapping Examples | Labels | Skills Loaded | Contexts Loaded | | --------------------------------------------- | ------------------------------------------------ | ----------------------------- | | `bug`, `lang:go`, `chain:btc` | `git-workflow`, `go-development` | bug-fix.md, chains/btc.md | | `enhancement`, `lang:typescript`, `chain:xrp` | `git-workflow`, `typescript-development` | feature-add.md, chains/xrp.md | | `documentation`, `scope:docs` | `git-workflow`, `docs-update` | documentation.md | | `refactoring`, `scope:db`, `lang:go` | `git-workflow`, `db-migration`, `go-development` | refactoring.md, db-change.md | | `test`, `lang:go`, `unit-test` | `git-workflow`, `go-development` | test.md | | `security`, `lang:go` | `git-workflow`, `go-development` | security.md | ## 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` ## Quick Reference ``` Required: [Type] + [Language OR Scope] Optional: [Test Scope] + [Chain] Type label → Context document (what to do) Lang/Scope label → Skill (how to do) Chain label → Chain context (domain knowledge) ``` ## Related - [Task Classification SSOT](../../../docs/guidelines/task-classification.md) - Label definitions - [GitHub Labels](.github/labels.yml) - Label configuration - `github-issue-creation` - Uses this mapping for issue creation - `fix-issue` command - Uses this mapping for issue work
Related Skills
wallet-cli
How to run watch, keygen, and sign wallet CLI commands. Use when executing wallet commands or testing wallet functionality.
typescript-development
TypeScript/JavaScript development workflow for apps/ directory. Use when modifying TypeScript code in xrpl-grpc-server or JavaScript in eth-contracts.
solidity-development
Solidity smart contract development workflow. Use when modifying smart contracts in apps/eth-contracts/contracts/.
shell-scripts
Shell script development workflow. Use when modifying files in scripts/ directory or any *.sh files.
openspec-propose
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
mockery
Mock generation workflow for go-crypto-wallet. Activate whenever a developer asks to generate a mock for a new interface, add test coverage that requires a mock, or replace a manually-written test stub for a ports interface. Claude MUST use `make mockery` — never write mock struct code by hand.
makefile-update
Makefile development workflow. Use when modifying Makefile or files in make/ directory.
knowledge-gap
Post-task knowledge gap review and proposals for improving skills/rules
go-development
Go development workflow including verification commands and self-review checklist. Use when modifying Go code in internal/, pkg/, or cmd/ directories.