Skip to content
Skills Library
Programming · Writing

vc:docs

/vc:docs

Use when you need to analyze a codebase and initialize, update, or summarize project documentation.

Repository
cuecards ↗
Licence
MIT
Last repository change
25.10.2026

Assessment and security

80/ 100Class: good
Format15 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
4
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when you need to analyze a codebase and initialize, update, or summarize project documentation.

Arguments

/vc:docs init|update|summarize
Original author description

Use when you need to analyze a codebase and initialize, update, or summarize project documentation.

How it works

  1. Default (No Arguments)
  2. Subcommands
  3. Routing
  4. Shared Context
Original SKILL.md headings · 41 lines, 200 words
SKILL.md preview
---
name: vc:docs
description: "Use when you need to analyze a codebase and initialize, update, or summarize project documentation."
argument-hint: "init|update|summarize"
metadata:
  author: claudekit
  version: "1.0.0"
---

# Documentation Management

Analyze codebase and manage project documentation through scouting, analysis, and structured doc generation.

## Default (No Arguments)

If invoked without arguments, use `AskUserQuestion` to present available documentation operations:

| Operation | Description |
|-----------|-------------|
| `init` | Analyze codebase & create initial docs |
| `update` | Analyze changes & update docs |
| `summarize` | Quick codebase summary |

Present as options via `AskUserQuestion` with header "Documentation Operation", question "What would you like to do?".

## Subcommands

| Subcommand | Reference | Purpose |
|------------|-----------|---------|
| `/vc:docs init` | `references/init-workflow.md` | Analyze codebase and create initial documentation |
| `/vc:docs update` | `references/update-workflow.md` | Analyze codebase and update existing documentation |
| `/vc:docs summarize` | `references/summarize-workflow.md` | Quick analysis and update of codebase summary |

## Routing

Parse `$ARGUMENTS` first word:
- `init` → Load `references/init-workflow.md`
- `update` → Load `references/update-workflow.md`
- `summarize` → Load `references/summarize-workflow.md`
- empty/unclear → AskUserQuestion (do not auto-run `init`)

## Shared Context

For this repo, durable agent-facing documentation lives in `process/context/`, not `./docs`.
Read `process/context/all-context.md` first to choose the relevant root file or context group.
Use `audit-context` after adding, moving, splitting, or grouping context files.

**IMPORTANT**: **Do not** start implementing code.
Files in this package (4)
  • SKILL.md 2 KB
  • references/init-workflow.md 2 KB
  • references/summarize-workflow.md 1 KB
  • references/update-workflow.md 3 KB

Versions

The database has no other skills named vc:docs.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 187914e03de7 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100update-docs
    Update public documentation in docs/public/ when features or tools change. Triggers on "/update-docs", "update docs", "update documentation".
  • 100documentation
    Use this skill when the user asks you to write, update, or fix project documentation — READMEs, API docs, user guides, ADRs, or other Markdown docs. Also use when code changes need user-facing docs updates. Only write Markdown files; do not use for implementation, planning or test work.
  • 100update-docs
    Update all project documentation to reflect the current state of the codebase. Use after finishing a feature, refactor, or any meaningful change — or whenever docs feel stale.
  • 100docs-update
    Audit project documentation against the current state of the codebase and produce a revision plan. Reads README and all docs, launches parallel Explore agents to verify claims, diffs documentation vs reality, and applies approved fixes. Use when user says "quality-docs-update",…
  • 100docs-update
    Use when the user needs to update, improve, audit, or maintain documentation in a project. Covers READMEs, changelogs, API docs, inline comments, missing docs, and overall documentation quality. Works well before releases or when documentation has fallen behind the code.
  • 100code-documentation
    Analyze source code repositories and create, update, and validate accurate technical documentation. Use when developers request README generation, API documentation, architecture documentation, codebase explanation, or documentation maintenance.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.