update-codemap

Refresh CODEMAP documentation by scanning src/ and updating docs/technical/CODEMAP.md.

70|42|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/tranhieutt/software_development_department --skill update-codemap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-codemap
Source: https://github.com/tranhieutt/software_development_department/tree/main/.claude/skills/update-codemap
Command: npx skills add https://github.com/tranhieutt/software_development_department --skill update-codemap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents CODEMAP from becoming stale and misleading other agents whenever the codebase evolves after merges, refactors, or directory changes.

Core Features & Use Cases

  • Scope-aware refresh keeps CODEMAP accurate by choosing between full updates and targeted sections tied to specific modules or areas.
  • Structure verification reads the existing documentation and scans src/ to capture modules, API routes, shared utilities, data models, and integrations.
  • Documentation hygiene appends entries to the revision history and highlights staleness indicators so future agents know when to rerun the skill.
  • Use Case: After a major feature merge, run this skill so CODEMAP reflects the new src/ structure and prevents downstream confusion.

Quick Start

Invoke update-codemap right after merging or refactoring so it rescans src/ and refreshes docs/technical/CODEMAP.md.

Frequently Asked Questions about update-codemap

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

FAQPage Schema
How do I keep technical docs aligned with the codebase after a major refactor?

Scanning src/ files to identify API route groups, utilities, and data models, then updating docs/technical/CODEMAP.md tables, keeps technical docs aligned after a refactor and prevents downstream confusion.

When should I update the CODEMAP for my project?

You should update the CODEMAP after significant merges, refactors, or adding new feature directories in src/ when the documentation threatens to become stale and mislead other agents working on the codebase.

What is the best way to document API route groups and shared utilities?

The best way to document API route groups and shared utilities is scanning src/ structure, verifying existing documentation, and updating docs/technical/CODEMAP.md tables to reflect current modules and integrations accurately.

Does updating a codemap require a full rewrite of the technical documentation?

A full rewrite is unnecessary; scope-aware refreshes allow targeted CODEMAP updates tied to specific modules or areas, appending revision history entries and highlighting staleness indicators for future agents.

Can I refresh specific sections of CODEMAP instead of the entire file?

Yes, scope-aware refreshes allow targeted updates tied to specific modules or areas, so you can refresh specific CODEMAP sections instead of rewriting the entire file after localized changes.