check

Validate project documentation against the Vibe Doc profile and report missing or stale Required docs.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/estevanhernandez-stack-ed/Vibe-Doc --skill check-estevanhernandez-stack-ed
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check
Source: https://github.com/estevanhernandez-stack-ed/Vibe-Doc/tree/main/packages/vibe-doc/skills/check
Command: npx skills add https://github.com/estevanhernandez-stack-ed/Vibe-Doc --skill check-estevanhernandez-stack-ed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that all Required documentation exists and is current before shipping, preventing deployment blockers due to missing or stale docs.

Core Features & Use Cases

  • Validate presence and freshness of Required docs across the project state.
  • Integrate with CI pipelines for automated checks and early feedback.
  • Generate or guide regeneration of missing/stale docs via the Scan/Generate workflow.

Quick Start

Run the check to verify that all required documentation is present and current.

Frequently Asked Questions about check

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

FAQPage Schema
How do I verify documentation readiness in a CI pipeline before deployment?

To check documentation readiness in CI, validate the project state against a documentation profile to output a pass/fail status with actionable guidance, preventing deploys with missing or stale docs.

What is a documentation gap-analysis check and when do I need it?

A documentation gap-analysis check identifies and reports missing or stale required docs by validating project state against a profile. You need it during CI or pre-deploy validation to prevent shipping with incomplete docs.

How do I prevent deploying with missing or stale documentation?

Prevent deploying with missing or stale documentation by running a pre-deploy validation check that identifies gaps against a docs profile and outputs actionable regeneration guidance for missing files.

Does the documentation validation check require any specific dependencies or environment setup?

The documentation validation check requires no external dependencies, but relies on existing Scan/Generate workflows and reads state from a .vibe-doc/state.json file to evaluate documentation freshness.

What happens when a required doc is missing during the pre-deploy validation?

When a required doc is missing during pre-deploy validation, the check outputs a fail status with actionable guidance and can trigger regeneration of missing files via the Scan/Generate workflow.