update-docs

Record session changes in agent_logs/LOG.md and update README.md with git commits.

4|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/kazhou/agents-toolkit --skill update-docs-kazhou
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-docs
Source: https://github.com/kazhou/agents-toolkit/tree/main/.claude/skills/update-docs
Command: npx skills add https://github.com/kazhou/agents-toolkit --skill update-docs-kazhou

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps keep project documentation in sync by automatically recording coding session changes and updating relevant files.

Core Features & Use Cases

  • Session logging: Prepend a formatted summary to agent_logs/LOG.md.
  • README updates: Update README.md when new features or changes are added.
  • Auto-commit: Commit documentation changes to the repository to preserve history.
  • Use Case: After a sprint or major update, run this skill to ensure docs reflect the latest work and decisions.

Quick Start

Run the update-docs skill after completing a coding session to prepend a session summary to agent_logs/LOG.md and update README.md with any new changes.

Frequently Asked Questions about update-docs

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

FAQPage Schema
How do I automatically update README and session logs after a coding session?

To automatically update documentation after a coding session, you need a tool that captures git diffs, prepends a formatted summary to agent_logs/LOG.md, conditionally updates README.md with new changes, and commits the documentation updates to the repository.

What is the best way to keep project documentation in sync with recent code changes?

Keeping project documentation in sync with recent code changes requires capturing session diffs and standardizing log formatting to ensure both your README.md and LOG.md accurately reflect the latest development work and decisions.

Can I automatically commit documentation updates to git after a development sprint?

Yes, you can automatically commit documentation updates to git after a development sprint by running an automation skill that records session changes and pushes the updated README.md and log files directly to the repository.

Does automatic documentation logging work without manual git diff capture?

Automatic documentation logging handles diff capture natively, so you do not need to manually extract git changes; the process identifies recent coding session updates and formats them into the log automatically.

When should I update README.md versus only logging session changes to LOG.md?

You should update README.md when new features or significant changes are added during a session, whereas standard session logging to LOG.md records the ongoing history of all development work and decisions.

What are the limitations of automating project documentation updates and git commits?

Limitations of automating project documentation updates include relying on standardized log formatting and conditional README rules, meaning the automation may lack context for complex architectural changes that require manual documentation refinement.