repo-map

Regenerate PROJECT_MAP.md and validate docs after repository layout changes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/StiensGate928/Srtforge --skill repo-map-stiensgate928
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-map
Source: https://github.com/StiensGate928/Srtforge/tree/main/.agents/skills/repo-map
Command: npx skills add https://github.com/StiensGate928/Srtforge --skill repo-map-stiensgate928

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

After file layout changes, this Skill helps maintainers refresh and validate the generated Srtforge project map to reflect the current repository structure.

Core Features & Use Cases

  • Automatically regenerates the PROJECT_MAP.md after edits to the repository structure.
  • Validates the integrity of the map by comparing it to current files and reference docs.
  • Use Case: after adding, removing, or moving files, directories, skills, or docs, run this Skill to ensure the map reflects the latest state.

Quick Start

Run the repo-map process to refresh and validate the generated project map after layout changes.

Frequently Asked Questions about repo-map

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

FAQPage Schema
How do I regenerate a project map after moving files in my repo?

You refresh the project map by running update_context.py through this Skill, which regenerates PROJECT_MAP.md to capture your latest file layout changes automatically.

How do I validate that my repository docs are fresh after layout changes?

You validate docs are fresh by running check_docs.py via this Skill, which compares the generated project map against current files and reference docs to verify integrity.

When do I need to refresh my repository project map?

You need to refresh your project map after adding, removing, or moving files, directories, skills, docs, contracts, scripts, or tests to ensure the map reflects the latest repository state.

Does updating the project map require any external dependencies?

Updating the project map requires no external dependencies; it runs internal scripts like update_context.py and check_docs.py to regenerate and validate your repository documentation.

What is the best way to automate project map validation for repository changes?

The best way to automate project map validation is running this Skill after layout edits; it executes update_context.py and check_docs.py to refresh PROJECT_MAP.md and verify doc integrity.