メニュー
Run one Evolver self-evolution cycle on the current repo (collect signals → select/mutate genes → propose changes). Use when the user asks to "run evolution cycle", "start evolver loop", or "run evolver strategy".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Show Evolver health — evolution memory location & size, recent log, and whether the full engine is installed. Use when the user asks for "evolver status", "evolver health", or "check evolver".
Self-evolution workflow for the agent. Before a substantive task, recall what worked on similar past tasks from evolution memory; after it, record the outcome so future sessions learn from it. Use when the user starts non-trivial work (a feature, a fix, a refactor) or asks the agent to "evolve", "learn from this", or "remember how this went".
Distill a reusable skill/gene from recent run history (optionally from an LLM response file). Use when the user asks to "distill skill", "extract gene", or "generalize lessons".
Run an evolution checkpoint — recall relevant past outcomes, reflect on the current task, and record what was learned. Use when the user requests an evolution checkpoint or asks to "evolve" or "checkpoint".
Review Evolver's pending evolved changes, then approve (solidify) or reject (roll back). Use when the user asks to "review changes", "accept evolver changes", or "discard/rollback evolver changes".
Solidify the current working changes into a durable Evolver gene/capsule (with rollback safety). Use when the user requests to "solidify changes", "save gene", or "capture this capsule".
| name | evolver-run |
| description | Run one Evolver self-evolution cycle on the current repo (collect signals → select/mutate genes → propose changes). Use when the user asks to "run evolution cycle", "start evolver loop", or "run evolver strategy". |
Execute an automated self-evolution cycle in the current git repository.
When requested, follow these steps:
Verify git environment — run git rev-parse --is-inside-work-tree. If we are not in a git repo, explain that Evolver requires git and stop.
Resolve CLI and execute:
EVOLVER="evolver"
command -v evolver >/dev/null 2>&1 || EVOLVER="npx -y @evomap/evolver"
Run the evolution cycle passing through strategy or looping arguments if requested (defaulting strategy to balanced):
EVOLVE_STRATEGY="balanced" $EVOLVER run
Summarize results — explain what changes occurred:
If there are pending changes, remind the user they can review and approve them using the evolver-review skill (e.g. npx @evomap/evolver review --approve), or roll them back if they are not to their liking. Do not auto-approve pending changes yourself; always leave that decision to the user.