labels-validate

Validate and align GitHub labels against a labels.yml configuration.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/oogDZ/2 --skill labels-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: labels-validate
Source: https://github.com/oogDZ/2/tree/main/.claude/skills/labels-validate
Command: npx skills add https://github.com/oogDZ/2 --skill labels-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Эта утилита обеспечивает консистентность ярлыков в GitHub с конфигурационным файлом labels.yml, упрощая аудит и поддержание порядка между Issues и PR.

Core Features & Use Cases

  • Валидирует структуру labels.yml и соответствие ярлыков в Issues/PR.
  • Автоматически обнаруживает несоответствия и подсказывает обновления.
  • Поддерживает аудит нескольких репозиториев и пакетную проверку после изменений labels.yml.

Quick Start

Запустите /labels-validate --sync, чтобы проверить и синхронизировать ярлыки между Issues и PR и файлом labels.yml.

Frequently Asked Questions about labels-validate

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

FAQPage Schema
How do I validate GitHub labels against a labels.yml configuration?

To validate GitHub labels against a labels.yml configuration, run /labels-validate to check the structure and alignment of labels across your Issues and PRs, ensuring consistency across repositories.

Can I synchronize GitHub labels across multiple repositories automatically?

Yes, you can synchronize GitHub labels across multiple repositories by running /labels-validate --sync, which detects mismatches between labels.yml and existing Issues or PRs and applies the necessary updates.

What is the best way to audit label consistency for GitHub Issues and PRs?

The best way to audit label consistency for GitHub Issues and PRs is to validate them against a labels.yml file, automatically discovering discrepancies to maintain governance across multiple repositories.

Does labels-validate require access to issue and pull request metadata?

Yes, labels-validate requires access to GitHub labels configuration and issue or pull request metadata to verify existing labels and support optional synchronization and validation options.

When do I need to run a labels.yml validation check?

You need to run a labels.yml validation check after making changes to your labels.yml file or during day-to-day audits to verify that existing labels on Issues and PRs remain consistent.