update-docs

Update package documentation to reflect code changes since the last push.

4|Updated Oct 10, 2025

Search Tags:#automation #git #documentation #packages #docs #update

Ready to run

npx skills add https://github.com/JanuaryLabs/deepagents --skill update-docs-januarylabs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: update-docs
Source: https://github.com/JanuaryLabs/deepagents/tree/main/.claude/skills/update-docs
Command: npx skills add https://github.com/JanuaryLabs/deepagents --skill update-docs-januarylabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Update package documentation across the repository to reflect code changes since the last push.

Core Features & Use Cases

Detect changes across packages and map them to the corresponding docs.
Update or regenerate documentation surfaces for affected packages and merge with existing content.
Use during releases or reviews to maintain a single source of truth for documentation.

Quick Start

Update all affected package docs to reflect code changes since the last push.

Frequently Asked Questions about update-docs

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

FAQPage Schema

How do I update package documentation to reflect code changes automatically?▼

You can update package documentation to reflect code changes by detecting modified files across packages, mapping them to existing docs, and spawning parallel sub-agents to refresh each affected package's documentation automatically.

What is the best way to keep documentation in sync with code changes across multiple packages?▼

The best way to keep documentation in sync is to detect changed files since the last git push, filter for existing docs in affected packages, and regenerate those documentation surfaces in parallel.

Does this documentation update approach work with existing docs or does it overwrite them?▼

This approach works with existing docs by filtering for them first, then updating or regenerating the documentation surfaces for affected packages and merging the new content with existing material.

When should I use an automated documentation update workflow for my packages?▼

You should use an automated documentation update workflow during releases or code reviews to maintain a single source of truth, ensuring all package docs accurately reflect code changes since the last push.

How does parallel sub-agent processing work for updating package docs?▼

Parallel sub-agent processing works by identifying all affected packages with changed files, then spawning concurrent sub-agents to refresh each package's documentation simultaneously and summarize the update results.