evolution-engine

Generates rule-change proposals from correction signals and git history patterns.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/LYGOLANG/fufan-cc-flow --skill evolution-engine-lygolang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: evolution-engine
Source: https://github.com/LYGOLANG/fufan-cc-flow/tree/main/.agents/skills/evolution-engine
Command: npx skills add https://github.com/LYGOLANG/fufan-cc-flow --skill evolution-engine-lygolang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Repeated AI coding mistakes and recurring fix patterns often go unaddressed because nobody systematically reviews correction signals or git history. This Skill digests pending correction signals and scans git logs to surface recurring failure patterns, then writes concrete rule-change proposals for user review instead of silently modifying anything. ## Core Features & Use Cases - Signal Digestion: Drains correction signals from .codex/evolution/signals.jsonl and converts them into actionable proposals written to proposals.md. - Git Pattern Mining: Scans git log and git diff to detect repeatedly occurring fix patterns that deserve a standing rule. - Bidirectional Rule Maintenance: Proposes both adding rules for confirmed failure modes and retiring rules that are internalized, never triggered, or duplicated. - Forced Abstraction: Strips product-specific names and terms from signals so rules capture product-agnostic general lessons, while project-specific instances go to user memory. - Use Case: After several sessions where the AI repeatedly made the same type of mistake, run this Skill to consolidate those corrections into a short list of rule proposals that the main Agent reviews with you one by one at session start. ## Quick Start Ask the AI to run the evolution-engine skill to digest pending correction signals and scan git history for recurring fix patterns, then review the proposals it writes.

Frequently Asked Questions about evolution-engine

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

FAQPage Schema
How do I turn repeated AI coding mistakes into permanent rules?▼

Run the evolution-engine skill to drain pending correction signals from signals.jsonl and scan git history for recurring fix patterns. It writes each finding as a proposal in proposals.md, which the main Agent reviews with you before any rule is changed.

How does the skill decide which failure patterns deserve a rule?▼

It applies a reproducibility test: a rule is only proposed if removing it would let the failure recur. It also enforces minimal intervention, preferring a single counterexample or an edit to an existing rule over creating new rules or skills.

Does the evolution engine modify rules or files by itself?▼

No. It only digests signals and writes proposals into the review section of proposals.md. The main Agent presents each proposal at session start, and changes are applied only after the user approves, partially approves, or rejects them.

What happens to product-specific details in correction signals?▼

Product names, domain terms, and specific values are stripped during digestion so rules capture product-agnostic general lessons. The stripped product-specific instances are routed to user memory rather than into standing rules.

Can the skill also remove outdated rules?▼

Yes. It scans existing rules for ones already internalized, never triggered, or duplicated by other rules, and proposes retiring them. The goal is to keep the net rule count trending downward.