update-docs

Delegate documentation updates to a sub-agent before creating a Pull Request.

1|Updated Jan 26, 2026

Search Tags:#automation #git #workflow #documentation #pull request #update

Ready to run

npx skills add https://github.com/arakitakashi/homework-coach-robo --skill update-docs-arakitakashi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: update-docs
Source: https://github.com/arakitakashi/homework-coach-robo/tree/main/.claude/skills/update-docs
Command: npx skills add https://github.com/arakitakashi/homework-coach-robo --skill update-docs-arakitakashi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of updating project documentation after implementation work is completed, reducing the burden on the main agent and ensuring consistency.

Core Features & Use Cases

Delegates Documentation: Offloads the task of updating CLAUDE.md and docs/implementation-status.md to a sub-agent.
Pre-PR Workflow: Designed to be used after implementation is finished but before creating a Pull Request.
Context Minimization: Prevents the main agent's context from being bloated by large documentation files.

Quick Start

Use the update-docs skill to delegate documentation updates after completing a feature implementation.

Frequently Asked Questions about update-docs

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

FAQPage Schema

How do I automate updating project documentation before a pull request?▼

You can automate updating project documentation before a pull request by delegating the task to a sub-agent. This offloads large file processing, minimizing the main agent's context consumption while ensuring CLAUDE.md and implementation-status.md reflect recent changes.

Why does my agent's context get bloated when updating CLAUDE.md?▼

Agent context gets bloated when updating CLAUDE.md because processing large documentation files directly consumes significant tokens. Delegating this documentation update task to a sub-agent prevents context bloat by offloading the heavy file processing from the main agent.

What is the best way to update implementation status docs after a feature?▼

The best way to update implementation status docs after a feature is using a sub-agent delegation workflow. It requires summarizing implementation details, steering directory paths, and optionally providing test coverage changes to accurately update docs/implementation-status.md.

Can I delegate documentation updates to minimize main agent context?▼

Yes, you can delegate documentation updates to minimize main agent context. This workflow offloads the processing of large files like CLAUDE.md to a sub-agent, ensuring the main agent's context remains free for core development tasks.

What information is needed to update project documentation via a sub-agent?▼

To update project documentation via a sub-agent, you need to provide summaries of implementation details, steering directory paths, and optionally test coverage changes. This ensures the sub-agent accurately updates CLAUDE.md and implementation-status.md.