Run any Skill in Manus with one click

validate

Stars32

Forks2

UpdatedJune 15, 2026 at 22:00

Run the docflow readiness gate before reporting docs complete: checks links, INDEX freshness, metadata, placeholders, and changelog names. Use after writing or editing docs.

Installation

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.

Run Skill in Manus

Source

MedAdemBHA

MedAdemBHA/docflow

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	validate
description	Run the docflow readiness gate before reporting docs complete: checks links, INDEX freshness, metadata, placeholders, and changelog names. Use after writing or editing docs.

validate

Goal: block objectively broken documentation before an agent reports work as complete.

Run

bash scripts/docflow-validate.sh --target <REPO ROOT>

If running from an installed plugin where scripts are not in the target repo, use the plugin script path.

Interpret

Errors are blockers. Fix them before saying the docs are complete.
Warnings are legacy/adoption cleanup. Report them, but they do not block unless the user asked for a strict cleanup.
Fresh scaffold placeholders are warnings because new repos intentionally start from templates.

Rules

Run after /docflow:author, /docflow:changelog, /docflow:repair, or any manual docs edit.
Regenerate INDEX.md before validation when files were added, renamed, or removed.
Keep the output concise: status, blockers, warnings worth acting on.

More from this repository

same repository

adopt

MedAdemBHA/docflow

Add docflow to a repo that already has docs, without rewriting them. Adds missing config, folders, helpers, agent guidance, and an adoption review. Use when docs already exist or doctor recommends adopt.

2026-06-1532

author

MedAdemBHA/docflow

Write a new doc in the right place with the right name. Use when asked to "write a doc", "where should this doc go", "add an ADR", "document this decision", "new spec", or "new feature plan".

2026-06-1532

changelog

MedAdemBHA/docflow

Record shipped work in the monthly changelog (append-only). Use when something ships or when asked "what changed", "add to changelog", "release notes", or "what shipped this month".

2026-06-1532

check

MedAdemBHA/docflow

Friendly docflow readiness check: one status, one reason, and the exact next command. Use when asked if docflow is set up, ready, or "what do I do next".

2026-06-1532

doctor

MedAdemBHA/docflow

Read-only docflow diagnosis: scans docs, config, changelog, and links, then recommends init, adopt, or repair. Use when asked "check docs setup", "should I set up docflow", "why is docflow not working", or "doctor".

2026-06-1532

init

MedAdemBHA/docflow

Set up docflow in a repo with no docs yet: scaffold the docs tree, write docflow.json, add agent guidance. Use when asked to "set up docflow", "initialize docs", "scaffold docs", or "make this repo use docflow".

2026-06-1532

name	validate
description	Run the docflow readiness gate before reporting docs complete: checks links, INDEX freshness, metadata, placeholders, and changelog names. Use after writing or editing docs.

validate

Goal: block objectively broken documentation before an agent reports work as complete.

Run

bash scripts/docflow-validate.sh --target <REPO ROOT>

If running from an installed plugin where scripts are not in the target repo, use the plugin script path.

Interpret

Errors are blockers. Fix them before saying the docs are complete.
Warnings are legacy/adoption cleanup. Report them, but they do not block unless the user asked for a strict cleanup.
Fresh scaffold placeholders are warnings because new repos intentionally start from templates.

Rules

Run after /docflow:author, /docflow:changelog, /docflow:repair, or any manual docs edit.
Regenerate INDEX.md before validation when files were added, renamed, or removed.
Keep the output concise: status, blockers, warnings worth acting on.