skills.rest
YaroslavKomarov
YaroslavKomarovCOMMUNITY
Explore all skills by this author →
GitHub

ai-factory.evolve

Analyzes project patches and context to generate SKILL.md improvement plans.

Updated Apr 6, 2026
Search Tags:#automation#codebase#skills#improvement#patches#evolve#ai-factory
One-click install
npx skills add https://github.com/YaroslavKomarov/ShedulerBot --skill ai-factory-evolve-yaroslavkomarov
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ai-factory.evolve
Source: https://github.com/YaroslavKomarov/ShedulerBot/tree/main/.claude/skills/evolve
Command: npx skills add https://github.com/YaroslavKomarov/ShedulerBot --skill ai-factory-evolve-yaroslavkomarov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates skill evolution for AI Factory by learning from project context, patches, and codebase patterns to improve performance over time.

Core Features & Use Cases

  • Patch-driven improvement: learn from .ai-factory/patches/*.md to identify recurring errors and prevention rules.
  • Context-driven enhancement: integrate project conventions and codebase patterns to tailor skills.
  • Guided evolution workflow: generate minimal, verifiable improvements to SKILL.md and related rules without rewriting existing structures.

Quick Start

Provide a targeted improvement plan by analyzing patches and project context.

Frequently Asked Questions about ai-factory.evolve

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

FAQPage Schema
How do I automate skill improvement from project patches?▼

Automating skill improvement from project patches involves analyzing .ai-factory/patches/*.md files to identify recurring errors and generate targeted, minimal updates to SKILL.md files without rewriting existing structures.

What is patch-driven skill evolution in an AI codebase?▼

Patch-driven skill evolution is the process of reading project patch histories and codebase conventions to generate verifiable improvement notes, tailoring installed skills to match specific project patterns over time.

How do I update SKILL.md files based on codebase conventions?▼

Updating SKILL.md files based on codebase conventions requires analyzing .ai-factory/DESCRIPTION.md alongside current skill rules to output precise improvement notes and modified guidance that aligns with project standards.

Do I need existing AI Factory patches to evolve project skills?▼

Yes, evolving project skills requires existing patch histories stored as .md files and project context descriptions to analyze recurring errors and guide targeted, project-specific improvements to installed skills.

What is the best way to prevent recurring codebase errors in automated skills?▼

The best way to prevent recurring codebase errors in automated skills is to extract prevention rules from patch histories and integrate them as minimal, verifiable improvements to existing skill guidance.

Why should I analyze patch histories instead of manually rewriting SKILL.md files?▼

Analyzing patch histories instead of manually rewriting SKILL.md files ensures guided, minimal evolution that preserves existing structures while applying targeted, context-driven improvements based on actual project errors.

Related Skills

Explore More Software Engineering Skills→
VeronikaVashkevichVeronikaVashkevich

aif-architecture

Generate architecture guidelines tailored to a project's tech stack.

Community
Advanced
lee-tolee-to
56

aif-evolve

Analyze patches and codebase patterns to write project-specific skill-context rules.

Community
Advanced
afterworkafterwork

aif-evolve

Analyze patches and codebase patterns to update aif-* skill-context rules.

Official
Advanced
vulikjulikvulikjulik

aif-evolve

Analyze project patches and codebase patterns to generate skill-context rules.

Community
Advanced