evonestlisted

# evonest Use this skill when the user asks to **analyze**, **improve**, or **evolve** a project with evonest, or when they mention: - "run evonest", "analyze my code", "find improvements" - "execute a proposal", "apply a proposal", "improve my project" - "run a full evolution cycle", "evolve my code" - "show proposals", "list proposals" - "evonest status", "evonest history" ## Available MCP Tools All tools take `project` (absolute path) as their first argument. | Tool | When to use | |------|-------------| | `evonest_init` | First time setup — creates `.noory/evonest/` in the target project | | `evonest_analyze` | Scan and save ALL improvements as proposals (no code changes) | | `evonest_improve` | Execute one proposal (blocks until complete; use `all=True` for batch) | | `evonest_evolve` | Full cycle: Observe → Plan → Execute → Verify → commit/PR | | `evonest_status` | Show project status summary | | `evonest_proposals` | List pending proposals | | `evonest_history` | Show cycle history | | `evonest_config` | Read or update `.noory/evonest/config.json` | | `evonest_identity` | Read or write `.noory/evonest/identity.md` | | `evonest_identity_refresh` | Re-draft identity.md by having Claude explore the project (returns current + draft for review) | | `evonest_backlog` | Manage the improvement backlog | | `evonest_stimuli` | Add a stimulus (external input for the next observe cycle) | | `evonest_decide` | Record a human decision (constrains LLM proposals) | | `evonest_prog