arch-docs

Generate and update repository architecture and file structure documentation from repository evidence.

2|1|Updated Feb 20, 2026

Search Tags:#architecture #documentation #markdown #repository #file structure

Ready to run

npx skills add https://github.com/vosslab/vosslab-skills --skill arch-docs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: arch-docs
Source: https://github.com/vosslab/vosslab-skills/tree/main/skills/arch-docs
Command: npx skills add https://github.com/vosslab/vosslab-skills --skill arch-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation or refresh of docs/CODE_ARCHITECTURE.md and docs/FILE_STRUCTURE.md, ensuring repository architecture and file layout are up-to-date and well-documented.

Core Features & Use Cases

Automated Documentation: Generates or updates the architecture and file structure documentation from the current repository state.
Repo Evidence Analysis: Uses repository files and configurations to base statements on observable evidence.
Consistency and Style: Applies Markdown and repository style guidelines for clear and consistent documentation.
Use Case: When you need to document or refresh repository architecture or file layout, this Skill ensures it's done efficiently and accurately.

Quick Start

/vosslab-skills:arch-docs

Frequently Asked Questions about arch-docs

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

FAQPage Schema

How do I generate repository architecture documentation in Markdown?▼

You can generate repository architecture documentation in Markdown by analyzing your repository files and configurations to automatically create or update docs/CODE_ARCHITECTURE.md and docs/FILE_STRUCTURE.md from the current repository state.

What is the best way to keep file structure documentation updated in a codebase?▼

The best way to keep file structure documentation updated is to automate the refresh of docs/FILE_STRUCTURE.md by analyzing current repository evidence and applying Markdown style guidelines for consistent and accurate documentation.

Can I document my repository file layout without manually writing Markdown?▼

Yes, you can document your repository file layout without manually writing Markdown by using automated tools that analyze current repository evidence and generate docs/FILE_STRUCTURE.md and docs/CODE_ARCHITECTURE.md based on observable files and configurations.

Does architecture documentation generation work with any repository file structure?▼

Yes, architecture documentation generation works with any repository file structure by analyzing current repository files and configurations to base documentation statements on observable evidence, ensuring accuracy across different layouts.

When do I need to refresh repository architecture and file structure documentation?▼

You need to refresh repository architecture and file structure documentation when you are a repository maintainer or developer ensuring documentation is accurate and up-to-date, typically after significant changes to files or configurations.

Why should I use automated documentation for repository architecture instead of manual editing?▼

You should use automated documentation for repository architecture because it bases statements on observable repository evidence and applies Markdown style guidelines, resulting in consistent and accurate documentation without the risk of manual errors or outdated information.