One-click install
npx skills add https://github.com/yologdev/yoyo-evolve --skill evolve-yologdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evolve
Source: https://github.com/yologdev/yoyo-evolve/tree/main/skills/evolve
Command: npx skills add https://github.com/yologdev/yoyo-evolve --skill evolve-yologdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Safely modify your own source code, test changes, and manage your evolution workflow, reducing risk when iterating on self-improvement.

Core Features & Use Cases

  • Self-analysis and self-modification workflow: read current source, plan changes, apply edits, run tests, and commit if tests pass.
  • Built-in safety and guardrails: follow strict rules before making changes, with journaling to track attempts.
  • Iterative learning and memory update: uses journals and memories to inform future changes and avoid regressions.

Quick Start

Instruct me to begin a self-evolution session by outlining a target improvement and desired tests, then I will start making changes and verify them with tests.

Frequently Asked Questions about evolve

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely modify my own source code without breaking existing functionality?

To safely modify source code, use a plan-then-change workflow that applies surgical edits, runs automated tests, and commits changes only when tests pass, rolling back automatically if failures occur.

What is a self-improvement workflow in software engineering?

A self-improvement workflow is an iterative process where a bot reads its own source code, plans targeted modifications, applies edits, verifies them with automated tests, and logs attempts in a journal to prevent regressions.

How do automated tests prevent regressions during iterative code changes?

Automated tests prevent regressions by running after each code modification; if tests fail, guarded rollbacks revert the changes, ensuring only passing modifications are committed to the source code.

Can I use journaling to track my code modification attempts across iterative sessions?

Yes, journaling tracks code modification attempts across iterative development sessions, using memories to inform future changes, preserve context, and avoid repeating past regressions during self-evolution.

What are the safety guardrails for automated code modification?

Safety guardrails for automated code modification require strict adherence to workflow rules, including planning changes before applying them, running tests, committing only on success, and performing guarded rollbacks if failures occur.

When should I not use automated self-modification for my codebase?

You should avoid automated self-modification when lacking strict workflow rules or automated tests, as the process relies on guarded rollbacks and journaling to safely manage iterative source code changes.