Skip to main content
skill CX Codex

label-context-mapping — Claude Code skill: GitHub labels to context

The label-context-mapping skill maps GitHub labels to context documents and development skills automatically. Use it when creating tasks or working on them—the right contexts and verification commands load on their own.

MIT 1 installs ★ 129 updated 2026-04-22

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add hiromaily/go-crypto-wallet --skill label-context-mapping -a claude-code
Open on GitHub

What label-context-mapping does

The skill is a central reference that connects every GitHub label (bug, enhancement, documentation, programming language, code scope) to a context document and a set of skills. When you create an issue or run fix-issue, the skill automatically determines which contexts to load and which verification commands to run.

Four types of mappings live in this skill: task type (bug, enhancement, refactoring, documentation, security, technical-debt, test) → context document; language (Go, TypeScript, Solidity) → development skill; scope (docs, devops, scripts, makefile, db, config, proto) → specialized skill; blockchain (btc, bch, eth, xrp) → domain context. Each mapping also lists verification commands: make go-lint, make go-test, truffle compile, and others.

To follow this skill, every issue needs at least two labels: one type label and one language or scope label. Chain labels (chain:btc, etc.) and test scope labels are optional. This keeps contexts separate and ensures verification steps don't get skipped.

What it helps with

  • Choose the right labels when creating a GitHub issue
  • Load the correct context and skills for a task
  • Run the right verification commands after changes
  • Keep labels consistent across different task types and code areas

Example prompts for the agent

  • Create an issue with type bug, language lang:go, and chain chain:btc
  • What contexts should I load for labels enhancement, lang:typescript, and chain:xrp?
  • Run verification for a task with labels refactoring, scope:db, lang:go

How to install label-context-mapping

1Skills CLI (Vercel)

npx skills add hiromaily/go-crypto-wallet --skill label-context-mapping -a claude-code

2Manually: put the files in place

~/.claude/skills/label-context-mapping/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/label-context-mapping/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about label-context-mapping

How do I install label-context-mapping in Claude Code?

Run npx skills add hiromaily/go-crypto-wallet --skill label-context-mapping -a claude-code, then check ~/.claude/skills/label-context-mapping/SKILL.md to verify.

What does label-context-mapping do?

The skill connects GitHub labels (task type, language, scope, blockchain) to context documents and development skills. When you create or work on an issue, the required contexts and verification commands load automatically.

Which labels are required?

Every issue needs one type label (bug, enhancement, refactoring, documentation, security, technical-debt, test) and one language or scope label (lang:go, lang:typescript, scope:docs, scope:devops, etc.). Other labels are optional.

Source text

SKILL.md · MIT
---
name: label-context-mapping
description: Maps GitHub labels to Skills and Context documents. Use when creating issues (github-issue-creation) or working on issues (fix-issue command).
---

# 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

© hiromaily · MIT · hiromaily/go-crypto-wallet

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set2

Project sponsors

Companies that keep this analytics open