context-updater

Audits and updates documentation and AI context files against recent git changes.

31|2|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/shaharia-lab/agento --skill context-updater-shaharia-lab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-updater
Source: https://github.com/shaharia-lab/agento/tree/main/.claude/skills/context-updater
Command: npx skills add https://github.com/shaharia-lab/agento --skill context-updater-shaharia-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documentation and AI context files like CLAUDE.md and README.md drift out of sync with the codebase after feature work and merged PRs, causing AI agents to make wrong assumptions and produce incorrect code. ## Core Features & Use Cases - Change Detection: Parses git history and merged PRs over a configurable time scope to identify what actually changed in the codebase. - Documentation Audit: Cross-references code changes against CLAUDE.md, README.md, docs/, and skill definitions to find outdated, incomplete, or missing coverage. - Surgical Updates: Applies minimal targeted edits and creates new docs for undocumented features while preserving existing style and structure. - Use Case: After a week of merged PRs, run the skill with scope "since last 7 days" to receive an audit report of every stale doc section plus the exact edits applied to fix them. ## Quick Start Ask the agent to check all documentation and context files for changes since the last 7 days and update anything outdated.

Frequently Asked Questions about context-updater

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

FAQPage Schema
How do I keep CLAUDE.md and README.md up to date after code changes?

Run the context-updater skill with a time scope such as "since last 7 days". It parses git history and merged PRs, cross-references changes against all documentation files, and applies surgical edits only where docs are inaccurate.

How to audit documentation against recent git commits?

The skill runs git log with a configurable --since window, fetches PR descriptions and linked issues via the GitHub CLI, then reads the actual changed code before comparing it against each documentation file for accuracy.

Does the documentation updater rewrite entire files?

No. It makes surgical, targeted edits only and never rewrites sections that are still accurate. It preserves existing document style, structure, and tone, and flags items needing human input such as screenshots.

Can it create new documentation for undocumented features?

Yes. For significant new features with no existing coverage, it creates user-facing docs in docs/ or adds developer sections to docs/development.md, following the style of existing files in the same directory.

What tools does the context updater require?

It uses Read, Grep, Glob, Bash, Edit, and Write tools, plus the git and GitHub CLI (gh) commands for commit history, PR details, and linked issue retrieval. No external packages are required.