ck:docs

Analyze codebases to generate, update, and summarize documentation in a docs/ directory.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/quanganh208/cookmate --skill ck-docs-quanganh208
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:docs
Source: https://github.com/quanganh208/cookmate/tree/main/.opencode/skills/docs
Command: npx skills add https://github.com/quanganh208/cookmate --skill ck-docs-quanganh208

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill centralizes and automates the creation, updating, and summarization of project documentation by analyzing the codebase and coordinating documentation agents, removing ad-hoc manual doc work and fragmentation.

Core Features & Use Cases

  • Init: analyze the repository, run parallel scouting, merge reports, and spawn a docs-manager agent to generate an initial set of docs in the docs/ directory.
  • Update: detect changes, run parallel document readers, merge findings, and coordinate a docs-manager agent to update README and docs while performing size checks.
  • Summarize: produce focused, quick codebase summaries for onboarding, audits, or high-level reviews using ck:scout outputs.
  • Integrations & Safeguards: orchestrates ck:scout and docs-manager workflows, uses docs/ as the source of truth, and includes post-generation size and validation checks.

Quick Start

Use the ck:docs skill with the init argument to analyze the codebase and generate the initial documentation into the docs/ directory.

Frequently Asked Questions about ck:docs

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

FAQPage Schema
How do I generate documentation for a codebase automatically?

To generate documentation for a codebase automatically, run the init command to analyze the repository, execute parallel scouting, merge reports, and spawn a docs-manager agent to create initial files in the docs/ directory.

What is the best way to update project documentation after code changes?

Updating project documentation after code changes involves detecting modifications, running parallel document readers, merging findings, and coordinating a docs-manager agent to update README and docs files while performing size checks.

How do I create a quick codebase summary for onboarding?

Creating a quick codebase summary for onboarding involves using a summarize function that produces focused, high-level overviews of the repository utilizing scouting outputs.

Can I validate documentation size and consistency after generation?

Yes, you can validate documentation size and consistency after generation because the workflow includes built-in post-generation size and validation checks to ensure quality.

Does automated codebase analysis work without manual configuration?

Automated codebase analysis works without manual configuration by orchestrating scouting agents and a docs-manager workflow that uses the docs/ directory as the source of truth.