| name | moai-alfred-issue-labels |
| version | 4.0.0 |
| created | 2025-11-11T00:00:00.000Z |
| updated | 2025-11-12T00:00:00.000Z |
| status | stable |
| description | Enterprise GitHub issue labeling orchestrator with semantic label taxonomy, AI-powered auto-labeling, label hierarchy system, workflow automation, issue triage acceleration, and stakeholder communication; activates for issue classification, label management, workflow automation, priority assignment, and team communication |
| keywords | ["github-labels","issue-triage","label-taxonomy","ai-labeling","workflow-automation","issue-classification","priority-management","team-communication","semantic-labels","enterprise-triage"] |
| allowed-tools | ["Read","Bash","AskUserQuestion","mcp__context7__resolve-library-id","mcp__context7__get-library-docs","WebFetch"] |
Enterprise GitHub Issue Labeling Orchestrator v4.0.0
Skill Metadata
| Field | Value |
|---|
| Skill Name | moai-alfred-issue-labels |
| Version | 4.0.0 Enterprise (2025-11-12) |
| AI Integration | ✅ Context7 MCP, semantic analysis, auto-classification |
| Auto-load | On issue creation/update for auto-labeling |
| Categories | Type, Priority, Status, Component, Custom |
| Lines of Content | 850+ with 13+ production examples |
| Progressive Disclosure | 3-level (taxonomy, patterns, automation) |
What It Does
Provides comprehensive issue labeling system with semantic taxonomy, AI-powered auto-labeling, label hierarchy, workflow automation, and stakeholder communication patterns.
Semantic Label Taxonomy
Type Labels
type: bug → Something isn't working correctly
type: feature → New capability or enhancement
type: refactor → Code restructuring without behavior change
type: chore → Maintenance tasks (dependencies, configs)
type: docs → Documentation improvements
type: test → Test suite improvements
type: security → Security vulnerability or hardening
type: performance → Performance optimization
type: infra → Infrastructure/DevOps changes
Priority Labels
priority: critical → Blocks production, urgent (SLA: 4 hours)
priority: high → Significant impact, schedule soon (SLA: 1 day)
priority: medium → Normal priority, standard schedule (SLA: 1 week)
priority: low → Nice to have, backlog (SLA: unbounded)
Status Labels
status: triage → Waiting for team analysis
status: investigating → Team actively investigating
status: blocked → Waiting for external dependency
status: ready → Ready for implementation
status: in-progress → Currently being worked on
status: review → In code review
status: testing → In QA/testing
status: done → Completed and verified
status: wontfix → Intentionally not fixing
status: duplicate → Duplicate of another issue
Component Labels
component: api → REST/GraphQL API
component: database → Database layer
component: auth → Authentication/Authorization
component: ui → User interface
component: performance → Performance-related
component: documentation → Docs and guides
component: infrastructure → DevOps/Cloud
component: sdk → Client SDK