draft-validate

Validate draft files against .claude drafts frontmatter and naming standards.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Этот модуль проверяет черновики в .claude/drafts/ на соответствие установленному стандарту: наличие frontmatter, корректная структура файла и правильное именование.

Core Features & Use Cases

  • Проверка наличия и валидности frontmatter (name, description и др. необходимые поля).
  • Проверка структуры файла и соответствия шаблону именования.
  • Поддержка одиночной проверки по указанному пути и пакетной проверки всех черновиков через --all.

Quick Start

Запустите /draft-validate [путь] [--all], чтобы проверить указанный черновик или все черновики в .claude/drafts.

Frequently Asked Questions about draft-validate

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

FAQPage Schema
How do I validate frontmatter and naming conventions in markdown drafts?

You can validate frontmatter and naming conventions in markdown drafts by running a validation command against a specific file path or an entire drafts directory to enforce required fields and structural rules.

What are the required frontmatter fields for draft files to pass validation?

Required frontmatter fields for draft files include name, description, and other specified metadata necessary to meet the drafting standard, ensuring files are consistent and ready for review.

Can I check all draft files in a directory at once instead of validating individually?

Yes, you can check all draft files in a directory at once by using the batch validation flag, which scans and validates every draft file in the specified drafts folder simultaneously.

Why does my draft file fail the structural rules check?

Your draft file fails the structural rules check when it lacks valid frontmatter, contains missing required metadata fields, or violates the established file naming conventions required for review readiness.

What is the best way to ensure drafts are consistent before review?

The best way to ensure drafts are consistent before review is to enforce required frontmatter fields, apply standardized naming conventions, and verify structural rules through an automated validation workflow.