skills.rest
DeathKnightH
DeathKnightHCOMMUNITY
Explore all skills by this author →
GitHub

context-aware-dev

Load path-aware context documents before code edits and update CHANGELOG entries.

Updated Aug 23, 2026
Search Tags:#changelog#documentation#api#spec#scope#context-aware#code-editing
One-click install
npx skills add https://github.com/DeathKnightH/context-skills --skill context-aware-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context-aware-dev
Source: https://github.com/DeathKnightH/context-skills/tree/main/skills/context-aware-dev
Command: npx skills add https://github.com/DeathKnightH/context-skills --skill context-aware-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about context-aware-dev

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

FAQPage Schema
How do I prevent documentation drift when refactoring code across multiple modules?▼

To prevent documentation drift during refactoring, enforce path-aware context loading by detecting the project root and locating the nearest CONTEXT.md before applying code edits. This ensures changes respect module boundaries and automatically syncs affected SPEC, API, and CHANGELOG documents.

What is path-aware context loading and how does it work for software projects?▼

Path-aware context loading is a mechanism that detects the project root via .git or AGENTS.md, locates the nearest module-level CONTEXT.md, and selectively loads SPEC, API, or RULES documents based on the configured scope before any code modifications occur.

How do I automatically update CHANGELOG entries when editing API and SPEC files?▼

Automatically update CHANGELOG entries by applying operation-driven document selection during code edits, analyzing cross-module impacts, and enforcing updates to module-level and scope-level CHANGELOG.md files with proper formatting rules after modifying API or SPEC files.

Can I load specific SPEC and RULES documents based on the type of code change I am making?▼

Yes, you can load specific documents based on your code change type. The system uses operation-driven document selection to pick SPEC.md, API.md, or RULES.md on demand, matching the change category such as interface, business logic, data model, UI, or configuration.

Does this context-aware code editing approach work with projects using AGENTS.md for root detection?▼

Yes, context-aware code editing supports projects using AGENTS.md by utilizing it for project-root detection alongside .git directories. It then locates the nearest CONTEXT.md and selectively loads relevant documentation according to your configured scope rules.

When should I use cascade-down scope mode instead of single scope for loading project context?▼

Use cascade-down scope mode when code edits require visibility into downstream module impacts, as it loads the nearest CONTEXT.md alongside higher-level maps. Single scope is sufficient for isolated edits that do not trigger cross-module impact analysis requirements.

Related Skills

Explore More Software Engineering Skills→
oozoofrogoozoofrog

agent-context-init

Analyze a repository to scaffold AGENTS.md, AGENTS.override.md, and CONTEXT.md files.

Community
Intermediate
qmuqmu
1

write-changelog

Generate changelog entries from archived tickets and update CHANGELOG.md.

Official
Intermediate
shanyan-wcxshanyan-wcx
96

trellis-check

Run lint, type checks, tests, and spec synchronization on codebases.

Community
Intermediate
kivo360kivo360
1

moai-change-logger

Track and audit project changes across files, code, and repository history.

Community
Advanced