Update Context Documentation

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.

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.

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.

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.

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.

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.