Menu
Reference for valid GitHub labels in HestAI-MCP repository to prevent label errors
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Supabase test harness patterns including local Supabase setup, test user creation via Auth Admin API, RLS testing, migration testing (db_reset), seed sequences, rate limiting, and environment detection. Use when setting up Supabase testing infrastructure, creating test users, troubleshooting Supabase test failures, or implementing RLS validation. Triggers on: supabase test setup, test user creation, supabase local testing, RLS testing, migration testing, supabase test harness, auth test helpers.
Supabase operational knowledge for migrations, RLS optimization, MCP tool benchmarks, and ADR-003 compliance. Use when validating database migrations, optimizing Row-Level Security policies, checking MCP tool performance, or ensuring Supabase operational standards. Triggers on: migration validation, RLS patterns, Supabase benchmarks, ADR-003, database state tracking, schema governance.
LLM-native structured communication format. Teaches OCTAVE syntax rules, canonical forms, and warning prevention for zero-error .oct.md authoring.
Advanced semantic vocabulary, holographic contracts, and structural patterns for OCTAVE. REQUIRES octave-literacy. Extends literacy with mythology, archetype annotation, v6 contracts, and anti-pattern rules.
Workflow for transforming prose into semantic OCTAVE structures. Covers tier selection, transformation phases, loss accounting, and decision rules. REQUIRES octave-literacy.
Strategic oversight mode for the Holistic Orchestrator. Episodic State Machine pattern with ho-liaison advisory (via pal_clink), run_debate escalation, and oa-router delegation. REPLACES holistic-orchestration when loaded.
| name | github-labels |
| description | Reference for valid GitHub labels in HestAI-MCP repository to prevent label errors |
| allowed-tools | ["Bash"] |
| trigger-patterns | ["gh issue create","create.*issue","github.*label","what labels","valid labels"] |
| auto-activation | true |
Prevents "label not found" errors when creating GitHub issues by providing agents with the current valid label taxonomy.
bug - Something isn't workingdocumentation - Improvements or additions to documentationduplicate - This issue or pull request already existsenhancement - New feature or requestgood first issue - Good for newcomershelp wanted - Extra attention is neededinvalid - This doesn't seem rightquestion - Further information is requestedwontfix - This will not be worked onadr - Architecture Decision Recordrfc - Request for Comments (deprecated per ADR-0060)priority:p0-critical - Blocking production or critical pathpriority:p1-high - Important, should be addressed soonpriority:p2-medium - Normal prioritypriority:p3-low - Nice to havephase:b1 - B1: Foundation phasephase:b2 - B2: Features phasephase:future - Future considerationarea:mcp-tools - MCP tool implementationarea:governance - Governance systemarea:ci-cd - CI/CD pipelinearea:agents - Agent systemstatus:blocked - Blocked by dependenciesstatus:needs-discussion - Needs team discussionstatus:implementation-pending - Approved, waiting for implementationstatus:draft - Draft/work in progressobsolete - No longer relevantmilestone:b1-foundation - B1 milestonemilestone:b2-features - B2 milestonemilestone:b3-integration - B3 milestoneepic - Epic tracking issueoctave-integration - OCTAVE integration workBefore creating a GitHub issue:
# 1. Verify current labels (labels can change over time)
gh label list --json name --jq '.[].name'
# 2. Create issue with ONLY valid labels
gh issue create \
--title "Issue Title" \
--label "enhancement,priority:p2-medium,phase:b1" \
--body "Issue description"
❌ Don't use:
p0, p1, p2, p3 (missing priority: prefix)b1, b2 (missing phase: prefix)mcp-tools, governance (missing area: prefix)✅ Do use:
priority:p0-critical, priority:p1-highphase:b1, phase:b2area:mcp-tools, area:governancegood first issue)The ~/.claude/hooks/pre_tool_use/validate-gh-labels.sh hook automatically:
gh issue create executesIf you see a warning, check this skill for the correct label names.
To get the current label list programmatically:
gh label list --json name,description --jq '.[] | "\(.name): \(.description)"'
This skill works in tandem with the label validation hook to:
If you need a new label that doesn't exist:
gh label create <name> --description "..." --color <hex>