ck:docs

Generate, update, and summarize project documentation from a codebase.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

There is no unified, automated method to generate and maintain project documentation directly from a codebase, leading to outdated or inconsistent docs.

Core Features & Use Cases

  • Init: generate initial documentation for new projects.
  • Update: refresh docs to reflect code changes.
  • Summarize: produce concise overviews of project status and architecture.

Quick Start

Initialize the project documentation for the current repository to generate initial docs.

Frequently Asked Questions about ck:docs

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

FAQPage Schema
How do I generate project documentation directly from my codebase?

To generate project documentation from your codebase, use the init subcommand to create initial docs. This process analyzes your software project and writes the required reference files into the docs directory.

What is the best way to keep codebase documentation updated after code changes?

The best way to keep codebase documentation updated is using the update subcommand. It refreshes existing project docs to accurately reflect recent code changes within your repository.

Can I produce an architectural summary for an existing software project?

Yes, you can produce an architectural summary for an existing software project. The summarize subcommand generates concise overviews of project status and architecture from your codebase.

Does this documentation workflow support software projects of any size?

Yes, this documentation workflow supports software projects of any size. It applies to any repository requiring initialization, updates, and summaries of project documentation.

Why does my project need automated documentation generation?

Your project needs automated documentation generation to prevent outdated or inconsistent docs. It provides a unified method to maintain project documentation directly from the codebase.

Where are the generated docs files written when initializing project documentation?

Generated docs files are written to the docs directory when initializing project documentation. The workflow coordinates with scout and docs-manager workflows to route tasks by subcommands.