agentleFS
Sign inStart free
metagit-aimetagit-ai/metagit-cli/skills/metagit-config-refresh/SKILL.md

metagit-config-refresh

Skill4 starsChanged 12 days agoMITView on GitHub

Refresh or bootstrap `.metagit.yml` using deterministic init/validate. Use when configuration is missing, stale, or incomplete for workspace operations.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 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.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Keep .metagit.yml accurate without dumping detect output into context.

    line 8
  2. Very specific:

    If missing: metagit init --kind application --no-prompt or skills/metagit-bootstrap/scripts/bootstrap-config.sh .

    line 13
  3. Very specific:

    If the file has includes:, edit the fragment that owns the field.

    line 16
  4. Distinctive:

    Prefer plan/dry-run for large updates.

    line 24
  5. Distinctive:

    Never overwrite a valid umbrella workspace mapping without confirmation.

    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

Refreshing Project Config

Keep .metagit.yml accurate without dumping detect output into context.

Workflow

  1. metagit config validate -c .metagit.yml (or note that the file is missing).
  2. If missing: metagit init --kind application --no-prompt or skills/metagit-bootstrap/scripts/bootstrap-config.sh .
  3. Optional enrich: metagit detect repository -p . -o summary, or --output-file .metagit/.detect/repository.json for the full payload. Do not run detect repo_map.
  4. Patch with metagit config patch / catalog commands. Re-validate.
  5. If the file has includes:, edit the fragment that owns the field. Do not replace the root with merged config show output. Split or flatten with metagit config split / metagit config flatten.

Output contract

Return config health before/after, a short update summary, and any manual follow-up. Do not paste full YAML.

Safety

  • Prefer plan/dry-run for large updates.
  • Never overwrite a valid umbrella workspace mapping without confirmation.

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