service-validate

To validate service documentation, run a check against your project standard to ensure proper frontmatter, mandatory sections like changelog and autonomy notes, and API/Data Model subsections. You can target a single service by name or all services at once.

Documentation validation requires a completed frontmatter with name and description, a changelog section, autonomy notes, and API/Data Model references. Your service spec must include all these mandatory subsections to meet the standard.

Yes, you can check all service docs at once by running the validation command with the --all flag. This iterates through every service specification file in your directory to enforce consistent frontmatter and structural compliance.

You should run service documentation validation during pre-commit checks, code reviews, or new service creation workflows. This ensures consistent frontmatter fields and API/Data Model details before changes are merged into the main branch.

Yes, documentation validation explicitly checks for missing API and Data Model references. It enforces the presence of these subsections within your service spec to ensure all technical interface details are properly documented.