context-aware-dev

What problem does it solve?

Editing code without the surrounding module and project context causes inconsistent changes, broken interfaces, and documentation drift; this Skill ensures edits are informed by the nearest CONTEXT.md and related documents so changes remain consistent with design intent.

Core Features & Use Cases

• Path-aware context loading: Locate the nearest module-level CONTEXT.md and selectively load higher-level maps according to scope modes (single, cascade-down, full-cascade).
• Operation-driven document selection: Pick SPEC.md, API.md, or RULES.md on demand based on the type of change (interface, business logic, data model, UI, configuration).
• Cross-module impact analysis: Detect when edits affect upstream/downstream modules and require coordinated updates across consumers.
• Automated documentation sync: Enforce updating module-level CHANGELOG.md and optional scope/root-level summaries, with clear formatting rules and emergency/experimental handling.
• Use case: Safely refactor an API endpoint while ensuring backward compatibility, updating SPEC and API docs, and recording the change in the appropriate CHANGELOG.

Quick Start

Before modifying a target file, load the nearest CONTEXT.md and related SPEC/API per scope rules, apply the code change, and update affected documentation and the module CHANGELOG.