code-evolution

Evolve existing codebases with minimal edits and regression validation.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/pycode4micro/bushserver --skill code-evolution-pycode4micro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-evolution
Source: https://github.com/pycode4micro/bushserver/tree/main/src/bushserver/seeds/skills/package/code-evolution
Command: npx skills add https://github.com/pycode4micro/bushserver --skill code-evolution-pycode4micro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of changing an established repository without breaking existing behavior by guiding you to understand current contracts first and then apply the smallest correct edits.

Core Features & Use Cases

  • Contract-first iteration: reads existing code contract summaries (context, diffs, and validation rules) before proposing changes, reducing unintended side effects.
  • Targeted minimal-change editing: supports precise feature additions, refactors, bug fixes, test additions, interface alignment, and performance work using minimal blast-radius rules.
  • Validation-driven completion: enforces an explicit regression verification step and requires cache refresh for modified files after passing validation.

Quick Start

Tell the agent: "Update the existing code so it correctly handles <your described behavior>, add the smallest necessary tests if required, and validate that the change preserves current behavior."

Frequently Asked Questions about code-evolution

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

FAQPage Schema
How do I refactor an existing codebase without breaking established contracts?

Refactoring an existing codebase without breaking contracts requires reading current context and diffs first, then applying minimal-diff edits guided by cached summaries to preserve behavior.

What is the best way to add a feature to an existing repository without causing regressions?

Adding a feature safely requires a regression-first validation approach, applying minimal blast-radius edits to the target scope and verifying that the change preserves current behavior.

How do I fix a bug in a codebase using minimal diff editing?

Fixing a bug with minimal diff editing involves reading existing code contract summaries before proposing changes, applying the smallest correct edits, and refreshing the cache for modified files.

Can I use this approach for interface alignment and test additions simultaneously?

Yes, interface alignment and test additions are supported by reading existing validation rules first, applying targeted minimal-change edits, and enforcing an explicit regression verification step.

Does regression validation require refreshing the cache after passing validation?

Yes, regression validation requires cache refresh for modified files after passing validation to ensure the contract summaries reflect the latest state of the codebase.

When should I not use minimal diff editing for code evolution?

Minimal diff editing is not suitable when the target scope is not understood or when changes require breaking established contracts, as it relies on reading context and validation rules beforehand.