ck:docs

Analyze a codebase to generate structured project documentation.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/mafvietnam/mafapp --skill ck-docs-mafvietnam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:docs
Source: https://github.com/mafvietnam/mafapp/tree/main/.claude/skills/docs
Command: npx skills add https://github.com/mafvietnam/mafapp --skill ck-docs-mafvietnam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze codebase to generate structured project documentation.

Core Features & Use Cases

  • Analyze codebase and generate a consistent set of docs (project overview, architecture, standards).
  • Update existing docs when the codebase changes by re-scanning and merging results.
  • Summarize the codebase to provide a quick, stakeholder-friendly overview.

Quick Start

Invoke the documentation workflow with no arguments to generate the initial docs from the current codebase.

Frequently Asked Questions about ck:docs

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

FAQPage Schema
How do I generate structured documentation from my codebase?

To generate structured documentation from your codebase, invoke the workflow with no arguments. It analyzes your code and outputs organized project overviews, architecture details, and standards under a dedicated docs directory.

What is the best way to update existing project docs when the codebase changes?

Updating existing project docs when the codebase changes is handled by re-scanning the codebase and merging results. This workflow keeps documentation synchronized with code modifications without overwriting previous manual additions.

Can I summarize a software project for stakeholders automatically?

You can automatically summarize a software project for stakeholders using the summarize workflow. It scans the codebase to provide a quick, stakeholder-friendly overview of project structure and core functionality.

Do I need a YAML frontmatter entry point for codebase documentation generation?

Yes, a YAML frontmatter entry point is required for codebase documentation generation. The workflow uses this entry point to apply routing rules and guide user interactions when organizing your project documentation structure.

Does the documentation workflow support optional resources directories like scripts and references?

Yes, the documentation workflow supports optional resources directories including scripts, references, and assets. These directories are analyzed alongside the codebase to ensure comprehensive documentation generation and accurate architectural summaries.