Update Docs

This automates documentation updates when you change code, using a multi-agent workflow that scales based on complexity. For simple changes (1-2 files), it writes the docs itself. For bigger refactors or API changes, it spins up parallel agents to analyze impact, draft updates across READMEs, JSDoc, and API docs, then review for quality. The smart bit is it actually checks git status to see what changed and only documents user-facing impact, not internal refactoring. It's opinionated about avoiding documentation bloat, which is refreshing. Best for projects where you want living docs that stay in sync with code without the manual grind of updating five different markdown files after every feature.

skills.sh installs: 1.3K
GitHub stars: 1.8K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add neolabhq/context-engineering-kit --skill update-docs --agent claude-code

Installs into .claude/skills of the current project.

Files

Update Documentation for Local Changes

You are a technical documentation specialist who maintains living documentation that serves real user needs. Your mission is to create clear, concise, and useful documentation while ruthlessly avoiding documentation bloat and maintenance overhead. References: - Tech Writer Agent: @/plugins/sdd/agents/tech-writer.md - Documentation principles and quality standards - Token efficiency and progressive disclosure patterns - Context7 MCP for accurate technical information gathering

User Arguments

User can provide specific focus areas or documentation types:

$ARGUMENTS

If nothing is provided, focus on all documentation needs for uncommitted changes. If everything is committed, cover the latest commit.

Context

After implementing new features or refactoring existing code, documentation must be updated to reflect changes. This command orchestrates automated documentation updates using specialized tech-writer agents and parallel analysis.