aif-evolve

Analyzes patches and codebase patterns to improve AI Factory skills with project-specific rules.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/1t1sCooL/zazyvala-bot --skill aif-evolve-1t1scool
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-evolve
Source: https://github.com/1t1sCooL/zazyvala-bot/tree/main/.cursor/skills/aif-evolve
Command: npx skills add https://github.com/1t1sCooL/zazyvala-bot --skill aif-evolve-1t1scool

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding assistants repeat the same mistakes because generic skill instructions lack project-specific knowledge. This Skill closes the loop by analyzing past fix patches, recurring bug patterns, and codebase conventions, then writing targeted rules that prevent future issues. ## Core Features & Use Cases - Incremental Patch Analysis: Processes patch files using a cursor-based system with an overlap window, extracting every independent prevention point and mapping it to the skills that should enforce it. - Skill-Context Rule Management: Writes project-specific rules to .ai-factory/skill-context/<skill-name>/SKILL.md without ever modifying built-in skill files, and detects stale, conflicting, or redundant rules when base skills are updated. - Gap Analysis & Evolution Reports: Compares prevention points against existing skill coverage, presents a traceable improvement report, and applies only user-approved changes with a logged evolution history. - Use Case: After accumulating 10 fix patches where 6 involve null-reference errors, run the evolve workflow to generate a rule for the fix skill that prioritizes null-check guards on optional database relations. ## Quick Start Ask the AI to run /aif-evolve with a skill name like "fix" or "all" to analyze accumulated patches and propose project-specific rule improvements.

Frequently Asked Questions about aif-evolve

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

FAQPage Schema
How do I improve AI coding skills based on past bug fixes?

Run /aif-evolve with a skill name or "all" to analyze accumulated patch files. It extracts prevention points from each patch, checks which ones existing skills already cover, and proposes new project-specific rules for your approval.

What is the difference between skill-context files and base SKILL.md files?

Base SKILL.md files inside skills/aif-* directories are owned by ai-factory and overwritten on updates. Skill-context files in .ai-factory/skill-context/ hold project-specific rules that override the base and survive updates.

Does aif-evolve modify built-in skill files directly?

No. It never edits files inside skills/aif-*/ directories because those are overwritten on update. All improvements for built-in skills are written to .ai-factory/skill-context/<skill-name>/SKILL.md instead.

How does incremental patch analysis with the cursor work?

A cursor file tracks the last processed patch filename, so only newer patches are analyzed on subsequent runs. An overlap window re-reads the newest five patches as a safety net, and the cursor only advances after improvements are applied.

What happens when a skill-context rule conflicts with an updated base skill?

The stale rule detection step classifies each rule as fully covered, conflicting, partially overlapping, or unique. Conflicts and overlaps are presented in a report, and you decide whether to keep, rewrite, narrow, or remove each skill-context rule.

When should I run a full rescan instead of incremental evolution?

Run a full rescan when the cursor references a deleted or renamed patch, or when you need a complete historical recount of prevention points. Delete the patch-cursor.json file and run /aif-evolve again.