structure-validate

Validate SSOT structure across README, .instructions/, folder tree, and links.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill validates the SSOT structure across core repository artifacts such as README, .instructions/, folder tree, and links. Use it after structural changes, during audits, or before releases to verify integrity.

Core Features & Use Cases

  • SSOT consistency checks across the repository (README, .instructions/, folder tree, and links)
  • Detection of broken links and missing references in the project structure
  • Pre-release structure validation to catch inconsistencies before deployment

Quick Start

Run the structure-validate command to verify the SSOT structure integrity of the repository.

Frequently Asked Questions about structure-validate

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

FAQPage Schema
How do I validate repository structure and check for broken links before a release?

Validate repository structure and broken links by running a validation check against README, .instructions/, the folder tree, and hyperlinks to detect inconsistencies before deployment. It inspects these artifacts and produces a deterministic report of any missing references.

What is SSOT structure validation and when do I need it?

SSOT structure validation is the process of verifying consistency across core project artifacts like documentation, folder trees, and links. You need it after structural changes, during audits, or before releases to verify repository integrity.

Can I detect missing references in my .instructions folder and README automatically?

Yes, you can detect missing references in your .instructions folder and README automatically. The validation process inspects these specific artifacts alongside the folder tree to enforce SSOT consistency rules and identify broken links.

How do I check folder tree integrity against project documentation?

Check folder tree integrity against project documentation by applying structural validation rules defined in the skill's configuration. This inspects the repository's physical folder structure and matches it against the documented SSOT artifacts.

What is the best way to audit project documentation for broken hyperlinks?

The best way to audit project documentation for broken hyperlinks is to run a pre-release structure validation that inspects all hyperlinks alongside the README and folder tree. This enforces SSOT checks and outputs a deterministic report of inconsistencies.