Menu
Regenerate CLAUDE.md from project constitution and specs
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Start a new change with Metta
Full lifecycle loop — discover, build, verify, ship
Resolve a reconciliation gap through the full metta change lifecycle
Resolve an issue through the full metta change lifecycle
Quick mode — small change without full planning
Finalize and ship the active change
| name | metta:refresh |
| description | Regenerate CLAUDE.md from project constitution and specs |
| allowed-tools | ["Read","Bash"] |
Run METTA_SKILL=1 metta refresh to regenerate CLAUDE.md from the project constitution (spec/project.md) and active specs (spec/specs/).
This updates all metta marker sections:
Use METTA_SKILL=1 metta refresh --dry-run to preview changes without writing.
Use METTA_SKILL=1 metta refresh --json for structured output.
After writing CLAUDE.md, METTA_SKILL=1 metta refresh automatically commits the regenerated file on your behalf using the commit message chore(refresh): regenerate CLAUDE.md. This prevents the regenerated file from silently contaminating subsequent unrelated commits.
If the repository is not a git working tree, has uncommitted changes to unrelated files, or the regenerated content is identical to the working copy, the auto-commit is skipped and the reason is surfaced in the command output.
Pass --no-commit to opt out of the auto-commit. This is the escape hatch for workflows that want to inspect the diff or stage CLAUDE.md as part of a larger commit. In that mode, METTA_SKILL=1 metta refresh writes the file and leaves staging and committing entirely up to you.
