maintain-filemap

What problem does it solve?

When a repository's directory structure changes — such as adding new top-level directories, mounting or unmounting submodules, or renaming major subsystems — the root FILEMAP.md quickly becomes stale. This leaves new collaborators without a clear, at-a-glance overview of the repo's layout, forcing them to clone the repo just to understand its structure.

Core Features & Use Cases

• Automated tree regeneration: Updates the depth-3 directory tree section of FILEMAP.md with a curated ignore list that filters out noise like node_modules, dist, and lock files, so the map stays readable.
• Preserves hand-written context: Keeps the curator-written preface that explains the purpose of each top-level directory, so the FILEMAP is useful for newcomers rather than just a raw tree dump.
• Flexible trigger options: Fires on directory shape changes, on a weekly cadence, or before releases, so teams can adopt the discipline that fits their workflow.
• Use case: When a team adds a new client-sites submodule to their pseudomonorepo, running this skill updates the parent FILEMAP.md to show the new submodule mount point (without listing its internal contents, which are documented in the submodule's own FILEMAP.md) so new contributors immediately understand the repo's top-level structure.

Quick Start

Use the maintain-filemap skill to regenerate the FILEMAP.md at your repo root after adding a new top-level directory or submodule.