Iterative Code Evolution
PassAudited by ClawScan on May 1, 2026.
Overview
This is a coherent instruction-only coding workflow skill that edits, runs, and logs code iterations in ways that match its stated purpose.
This skill appears safe for its intended use, but install it knowing that it can guide the agent to edit your code, run verification commands, and create a persistent `.evolution/` history. Use version control, review changes before accepting them, and keep sensitive information out of the evolution log.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent may make real changes to your repository when the skill is used.
The skill instructs the agent to change code files. That is expected for an iterative code-improvement skill, but it is still authority to mutate the user's project.
3. **Mutate** — Implements only the planned changes
Use it in a version-controlled project, review the proposed plan and diffs, and keep backups or commits so changes can be reverted.
Running project code can have side effects depending on the project, tests, or scripts being executed.
The verification phase involves running the code. This is central to the stated purpose, and the README discloses retry and revert behavior, but users should notice that execution is part of the workflow.
4. **Verify** — Runs the code; up to 3 retries on crashes, then reverts
Run this skill only on trusted projects or in a safe development environment, and clarify which tests or commands should be used for verification.
The log may preserve design details, failures, assumptions, or other project-specific context and may steer later edits.
The skill stores an iteration log and learned principles that can influence future cycles. This is disclosed and purpose-aligned, but it is persistent project memory.
The skill maintains an `.evolution/` directory in your project: `.evolution/ log.json ... variants/`
Review the `.evolution/` contents, avoid logging secrets, and delete or correct the log if it contains bad assumptions or sensitive information.