agentleFS
Sign inStart free
p10ns11yp10ns11y/skills/src-tree-reorganize/SKILL.md

src-tree-reorganize

Skill2 starsChanged 40 days agoMITView on GitHub

Reorganize scattered C/C++ sources into src/ with CMake updates. Use when user asks to tidy layout, move files to src, or clean root-level clutter.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After MVU refactor when file layout is still messy

    line 12
  2. Distinctive:

    Do not edit the user's attached plan file if one exists.

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Src tree reorganize

When to use

  • User wants sources moved from repo root into src/ (or similar tidy-up)
  • "make the project neat", scattered .c / .h at top level
  • After MVU refactor when file layout is still messy

Steps

  1. Glob all *.c, *.h, and CMakeLists.txt under {REPO_ROOT}.
  2. Grep includes and add_executable / target_sources references.
  3. Propose target layout (e.g. src/, include/) — minimal moves per step.
  4. Write / StrReplace paths in CMake and #include lines together.
  5. Shell cmake --build (or project build command) after each batch of moves.
  6. Summarize what moved and what still references old paths.

Constraints

  • Do not edit the user's attached plan file if one exists.
  • One logical batch per user "proceed" — build between batches.

Done when

Tree matches agreed layout and build passes.

Example provenance: premflow.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free