Validates that project structure documented in README.md accurately reflects the actual filesystem structure
Validates that project structure documented in README.md accurately reflects the actual filesystem structure
Tool Paths: Commands in this skill use default Windows paths from
{directories.config}/tools.json. See Configuration Guide to customize for your environment.
Validates that the project structure documented in README.md accurately reflects the actual filesystem structure. This skill ensures documentation stays synchronized with the codebase as the project evolves.
Execute the validation script to check if README matches actual structure:
C:\App\Anaconda\python.exe {directories.scripts}/validate_readme_structure.py --check
Expected output if valid:
✓ README project structure is up to date
agents: 7
skills: 18
blueprints: 14
patterns: 48
knowledge: 42
templates: 163
Expected output if invalid:
✗ README project structure is OUT OF DATE
Discrepancies found:
- skills: README says 14, actual is 18
- blueprints: README says 7, actual is 14
If discrepancies are found, review what changed:
# Generate current structure to see what's different
C:\App\Anaconda\python.exe {directories.scripts}/validate_readme_structure.py --generate
If discrepancies are legitimate (new components added), update the README:
C:\App\Anaconda\python.exe {directories.scripts}/validate_readme_structure.py --update
This automatically updates the Project Structure section in README.md.
Run validation again to confirm the update was successful:
C:\App\Anaconda\python.exe {directories.scripts}/validate_readme_structure.py --check
Add to .git/hooks/pre-commit (or use pre-commit framework):
#!/bin/bash
python {directories.scripts}/validate_readme_structure.py --check
if [ $? -ne 0 ]; then
echo "README structure validation failed. Run: python {directories.scripts}/validate_readme_structure.py --update"
exit 1
fi
The validation is integrated into .github/workflows/ci.yml:
- name: Validate README Structure
run: python {directories.scripts}/validate_readme_structure.py --check
When extending the factory with new components:
--check to see the discrepancy--update to fix README| Command | Description |
||-|
| --check | Validate README against actual structure (default) |
| --generate | Print the correct structure markdown |
| --update | Update README.md in place |
| --json | Output scan results as JSON (for tooling) |
| --root PATH | Specify project root directory |
| Component | Location | Counted |
|--|-||
| Agents | {directories.agents}/*.md | Number of .md files |
| Skills | {directories.skills}/*/SKILL.md | Directories with SKILL.md |
| Blueprints | {directories.blueprints}/*/blueprint.json | Directories with blueprint.json |
| Patterns | {directories.patterns}/**/*.json | All JSON files in subdirectories |
| Knowledge | {directories.knowledge}/*.json | All JSON files |
| Templates | {directories.templates}/**/*.tmpl | All .tmpl files |
This skill supports the factory's documentation-first approach:
onboarding-architect when validating project state--check in CI to fail builds with outdated documentation{directories.scripts}/validate_readme_structure.py.github/workflows/ci.ymlREADME.md (Project Structure section)This skill should be used when strict adherence to the defined process is required.
Search for places (restaurants, cafes, etc.) via Google Places API proxy on localhost.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Start voice calls via the OpenClaw voice-call plugin.
Notion API for creating and managing pages, databases, and blocks.
Gemini CLI for one-shot Q&A, summaries, and generation.
Category:developer