Update Context Documentation

Name: Update Context Documentation
Availability: InStock
Author: madhavmadupu

Review code changes and closed issues to suggest context documentation updates.

Updated Feb 10, 2026

Search Tags:#git #developer tools #code review #documentation #context #knowledge management

Ready to run

npx skills add https://github.com/madhavmadupu/atlas-mobile --skill update-context-documentation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Update Context Documentation
Source: https://github.com/madhavmadupu/atlas-mobile/tree/main/.agent/skills/update-context
Command: npx skills add https://github.com/madhavmadupu/atlas-mobile --skill update-context-documentation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps ensure that your project's context documentation is kept up-to-date with code changes and completed work, preventing outdated or missing information.

Core Features & Use Cases

Automated Change Review: Analyzes git logs and closed issues to identify relevant code changes.
Contextual Documentation Mapping: Suggests specific documentation files that likely need updates based on the nature of the code changes.
Guided Updates: Assists in reviewing current documentation, proposing changes, and ensuring final commits reflect the actual state of the project.
Use Case: After merging a feature branch that introduced a new API endpoint and modified a core domain rule, this Skill will identify the relevant commits and issues, then suggest updating docs/context/modules/<module-name>.md and docs/context/domain/<domain-name>.md.

Quick Start

Use the update context skill to review recent changes and suggest documentation updates.

Frequently Asked Questions about Update Context Documentation

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

FAQPage Schema

How do I keep documentation in sync with code changes after merging a feature?▼

To keep documentation in sync, this Skill reviews recent git commits and closed issues to map code modifications to specific context files, then proposes factual updates for domain rules and module APIs.

What is the best way to update project context documentation automatically?▼

The best way to update context documentation is by analyzing git logs and closed issues to identify relevant code changes, cross-referencing them with story requirements to suggest concise updates for affected documentation files.

How do I map code modifications to specific documentation files like domain rules?▼

You can map code modifications to documentation files by cross-referencing commits with story requirements, which allows the Skill to suggest updates for specific files like domain rules, module APIs, and current state overviews.

Does this documentation update tool work with my existing git workflow?▼

Yes, the tool integrates with your existing git workflow by analyzing git logs and cross-referencing closed issues with story requirements to ensure your project context documentation accurately reflects the actual state of the codebase.

Can I use this to identify which documentation files need updates after a code review?▼

Yes, you can use this Skill after a code review to identify relevant code changes and suggest specific documentation files that likely need updates, such as those detailing module APIs or domain rules.

When do I need to review context documentation for outdated information?▼

You need to review context documentation for outdated information after merging code changes, as this Skill cross-references commits with completed work to propose factual, concise updates preventing missing or stale project details.