amama-label-taxonomy

Automate GitHub issue labeling with priority, status, and routing labels.

1|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/Emasoft/ai-maestro-assistant-manager-agent --skill amama-label-taxonomy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: amama-label-taxonomy
Source: https://github.com/Emasoft/ai-maestro-assistant-manager-agent/tree/main/skills/amama-label-taxonomy
Command: npx skills add https://github.com/Emasoft/ai-maestro-assistant-manager-agent --skill amama-label-taxonomy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing GitHub issue labels, priorities, and status taxonomy consistently across teams is error-prone and hard to audit. This skill provides a centralized taxonomy and automated guidance that aligns labeling with governance rules and reduces mislabeling.

Core Features & Use Cases

  • Canonical priority and status labels (priority:critical, priority:high, priority:normal, priority:low; status: backlog, todo, in-progress, ai-review, human-review, merge-release, done, blocked) and mapping to kanban flows.
  • Guidance for creating new issues with standard labels, updating labels when requirements change, and generating status reports for users.
  • Facilitates human review routing by marking tasks for AI or human review and transitioning to merge/release when approved.

Quick Start

Create a new GitHub issue and apply the standard backlog status and initial priority/type labels using the taxonomy.

Frequently Asked Questions about amama-label-taxonomy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize GitHub issue labeling across multiple teams?

Standardize GitHub issue labeling by applying a centralized taxonomy that maps canonical priority and status labels to Kanban flows, ensuring consistent governance and reducing mislabeling across teams.

What is the best way to automate GitHub issue priority and status governance?

Automate GitHub issue governance by using label mappings, Kanban column definitions, and validation rules that apply safe defaults to prevent conflicting priority and status labels during issue creation and updates.

How does human review routing work for GitHub issues in a Kanban workflow?

Human review routing marks GitHub issues with specific status labels like ai-review or human-review, transitioning them to merge-release upon approval to maintain clear Kanban workflow visibility.

Can I generate status reports from standardized GitHub issue labels?

Generate status-friendly reports from standardized GitHub issue labels by applying the taxonomy's priority, status, and routing mappings to extract consistent project governance data.

Why do I need label validation to prevent conflicting labels on GitHub issues?

Label validation prevents conflicting labels on GitHub issues by enforcing safe defaults and canonical mappings, ensuring that priority and status tags remain auditable and aligned with governance rules.

Does this automated labeling taxonomy support custom priority levels beyond critical, high, normal, and low?

The labeling taxonomy supports canonical priority levels of critical, high, normal, and low, mapping them directly to Kanban flows rather than offering custom priority scales.