update-tree.md

Regenerate a timestamped TREE.md with excluded noisy directories.

Updated Nov 24, 2025

Search Tags:#automation #maintenance #devtools #filesystem #project-structure #tree-generation

Ready to run

npx skills add https://github.com/greentcsolutions-lab/tc-helper-app --skill update-tree-md

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: update-tree.md
Source: https://github.com/greentcsolutions-lab/tc-helper-app/tree/main/.claude/skills/update-tree-md
Command: npx skills add https://github.com/greentcsolutions-lab/tc-helper-app --skill update-tree-md

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Regenerates TREE.md after filesystem changes (new files/folders, moves, deletions) to keep repository structure documentation accurate and concise by excluding noisy directories.

Core Features & Use Cases

Excludes noisy artifacts such as node_modules, .next, dist, build, .cache, and other noise to produce a compact tree.
Regenerates TREE.md by executing a filtered tree command, captures the output, and writes a timestamped, Markdown-formatted tree back to TREE.md.
Useful after structural changes to automatically align documentation with the actual project layout.

Quick Start

Use after any filesystem changes to refresh TREE.md with a clean, up-to-date project tree.

Frequently Asked Questions about update-tree.md

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

FAQPage Schema

How do I automatically regenerate a project structure tree in markdown after moving files?▼

To automatically regenerate a project structure tree, this Skill executes a filtered filesystem command and writes a timestamped, markdown-formatted tree directly to TREE.md, accurately reflecting recent file moves and additions.

How can I generate a compact directory tree for my repository while excluding node_modules and build artifacts?▼

Generating a compact directory tree is handled by applying exclusions for noisy artifacts like node_modules, dist, build, and .cache, ensuring the outputted TREE.md remains concise and focused on source files.

What is the best way to keep filesystem documentation in sync with actual project layout changes?▼

Keeping filesystem documentation in sync is achieved by regenerating TREE.md after structural changes, capturing the current project layout and overwriting outdated documentation with an accurate, timestamped markdown tree.

Does this tree generation tool require any dependencies to output a markdown project structure?▼

No dependencies are required to output a markdown project structure, as the Skill operates independently to execute filtered filesystem commands and write the captured directory tree directly into TREE.md.

When should I refresh my repository tree file to maintain accurate documentation?▼

You should refresh your repository tree file immediately after any structural filesystem changes, such as adding new folders, moving directories, or deleting files, to ensure TREE.md stays in sync.