How do I install the Codemap Sync skill?

Run npx skillmds@latest add auto-skiller/codemap-sync in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Codemap Sync safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Codemap Sync?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Codemap Sync free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Codemap Sync?

Auto-Skiller (@auto-skiller) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Codemap Sync by auto-skiller — Agent Skill

Name: Codemap Sync
Rating: 4.666666666666667 (3 reviews)
Author: Auto-Skiller

File contents

Generated by: PROP-EXT-OM-03-CODING-STANDARDS

Update Codemaps

Analyze the codebase structure and generate token-lean architecture documentation.

Step 1: Scan Project Structure

Identify the project type (monorepo, single app, library, microservice)
Find all source directories (src/, lib/, app/, packages/)
Map entry points (main.ts, index.ts, app.py, main.go, etc.)

Step 2: Generate Codemaps

Create or update codemaps in docs/CODEMAPS/ (or .reports/codemaps/):

File	Contents
`architecture.md`	High-level system diagram, service boundaries, data flow
`backend.md`	API routes, middleware chain, service → repository mapping
`frontend.md`	Page tree, component hierarchy, state management flow
`data.md`	Database tables, relationships, migration history
`dependencies.md`	External services, third-party integrations, shared libraries

Codemap Format

Each codemap should be token-lean — optimized for AI context consumption:

# Backend Architecture

## Routes
POST /api/users → UserController.create → UserService.create → UserRepo.insert
GET  /api/users/:id → UserController.get → UserService.findById → UserRepo.findById

## Key Files
src/services/user.ts (business logic, 120 lines)
src/repos/user.ts (database access, 80 lines)

## Dependencies
- PostgreSQL (primary data store)
- Redis (session cache, rate limiting)
- Stripe (payment processing)

Step 3: Diff Detection

If previous codemaps exist, calculate the diff percentage
If changes > 30%, show the diff and request user approval before overwriting
If changes <= 30%, update in place

Step 4: Add Metadata

Add a freshness header to each codemap:

<!-- Generated: 2026-02-11 | Files scanned: 142 | Token estimate: ~800 -->

Step 5: Save Analysis Report

Write a summary to .reports/codemap-diff.txt:

Files added/removed/modified since last scan
New dependencies detected
Architecture changes (new routes, new services, etc.)
Staleness warnings for docs not updated in 90+ days

Tips

Focus on high-level structure, not implementation details
Prefer file paths and function signatures over full code blocks
Keep each codemap under 1000 tokens for efficient context loading
Use ASCII diagrams for data flow instead of verbose descriptions
Run after major feature additions or refactoring sessions

---name: codemap-syncdescription: Analyzes codebase structure and generates token-lean architecture documentation in codemap files, with diff detection and metadata tracking.---# Generated by: PROP-EXT-OM-03-CODING-STANDARDS---# Update CodemapsAnalyze the codebase structure and generate token-lean architecture documentation.## Step 1: Scan Project Structure1. Identify the project type (monorepo, single app, library, microservice)2. Find all source directories (src/, lib/, app/, packages/)3. Map entry points (main.ts, index.ts, app.py, main.go, etc.)## Step 2: Generate CodemapsCreate or update codemaps in `docs/CODEMAPS/` (or `.reports/codemaps/`):| File | Contents ||------|----------|| `architecture.md` | High-level system diagram, service boundaries, data flow || `backend.md` | API routes, middleware chain, service → repository mapping || `frontend.md` | Page tree, component hierarchy, state management flow || `data.md` | Database tables, relationships, migration history || `dependencies.md` | External services, third-party integrations, shared libraries |### Codemap FormatEach codemap should be token-lean — optimized for AI context consumption:```markdown# Backend Architecture## RoutesPOST /api/users → UserController.create → UserService.create → UserRepo.insertGET /api/users/:id → UserController.get → UserService.findById → UserRepo.findById## Key Filessrc/services/user.ts (business logic, 120 lines)src/repos/user.ts (database access, 80 lines)## Dependencies- PostgreSQL (primary data store)- Redis (session cache, rate limiting)- Stripe (payment processing)```## Step 3: Diff Detection1. If previous codemaps exist, calculate the diff percentage2. If changes > 30%, show the diff and request user approval before overwriting3. If changes <= 30%, update in place## Step 4: Add MetadataAdd a freshness header to each codemap:```markdown```## Step 5: Save Analysis ReportWrite a summary to `.reports/codemap-diff.txt`:- Files added/removed/modified since last scan- New dependencies detected- Architecture changes (new routes, new services, etc.)- Staleness warnings for docs not updated in 90+ days## Tips- Focus on **high-level structure**, not implementation details- Prefer **file paths and function signatures** over full code blocks- Keep each codemap under **1000 tokens** for efficient context loading- Use ASCII diagrams for data flow instead of verbose descriptions- Run after major feature additions or refactoring sessions

Frequently asked questions

Codemap Sync