context-updater

Automate updates to project_context.md after major codebase changes.

Updated Sep 23, 2025
One-click install
npx skills add https://github.com/hongliangc/combo_demon --skill context-updater
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-updater
Source: https://github.com/hongliangc/combo_demon/tree/main/.claude/skills/context-updater
Command: npx skills add https://github.com/hongliangc/combo_demon --skill context-updater

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps the project's contextual documentation up to date as your codebase evolves, preventing drift between implementation and architectural notes.

Core Features & Use Cases

  • Automated context updates on major changes (new features, refactors, architecture changes).
  • Concise per-module entries limited to three lines.
  • Automatic integration into .claude/context/project_context.md.

Quick Start

Trigger the context updater after completing a major change to regenerate the project_context.md.

Frequently Asked Questions about context-updater

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

FAQPage Schema
How do I automatically update project context documentation after refactoring?

Automatically update project context documentation after refactoring by triggering an automation skill that regenerates project_context.md. It enforces concise architectural entries limited to three lines per module to prevent implementation drift.

What is the best way to maintain architecture-level documentation during active development cycles?

The best way to maintain architecture-level documentation is to automate updates whenever major codebase changes occur. This ensures your context remains an up-to-date reference reflecting new features and structural modifications throughout development cycles.

How does automated project context updating handle per-module documentation limits?

Automated project context updating handles per-module documentation limits by enforcing concise entries restricted to a maximum of three lines per module. Updates are stored directly in the .claude/context/project_context.md file path.

Do I need to manually trigger context updates after adding new features to my codebase?

You do not need to manually trigger context updates after adding new features. You trigger the context updater once a major change is complete, and it automatically regenerates the project_context.md file to reflect the new architecture.

Can I synchronize my project context notes with codebase changes without writing manual documentation?

You can synchronize project context notes with codebase changes by applying automated context updates upon completing major modifications. This process integrates directly into .claude/context/project_context.md without requiring manual documentation writing.

When should I use automated context updates for my architectural notes?

Use automated context updates for architectural notes whenever major changes occur in your codebase, specifically targeting feature additions, refactors, and structural architecture changes to keep your development reference accurate.