skills.rest
lee-to
lee-toCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

aif-evolve

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

56|3|Updated Mar 17, 2026
Search Tags:#automation#governance#project-context#patch-analysis#evolve#ai-factory#skill-context
One-click install
npx skills add https://github.com/lee-to/ai-workspace --skill aif-evolve-lee-to
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aif-evolve
Source: https://github.com/lee-to/ai-workspace/tree/main/.claude/skills/aif-evolve
Command: npx skills add https://github.com/lee-to/ai-workspace --skill aif-evolve-lee-to

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to continuously improve AI Factory skills by analyzing project context, accumulated patches, and codebase patterns to identify gaps and reduce recurring issues across projects.

Core Features & Use Cases

  • Self-improvement loop: analyzes patches, context, and conventions to generate project-specific skill-context rules.
  • Guardrails and governance: uses skill-context overrides to tailor base skills to the project.
  • Cross-project consistency: ensures evolved skills behave consistently across related projects.

Quick Start

Run /aif-evolve to begin analyzing patches and updating skill-context rules.

Frequently Asked Questions about aif-evolve

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

FAQPage Schema
How do I automate skill governance and generate project-specific rules from codebase patches?▼

To automate skill governance, you can analyze accumulated patches and codebase patterns to generate concrete, traceable rules. This process identifies recurring issues and writes project-specific overrides directly into skill-context files.

What is the best way to prevent recurring codebase issues across multiple related projects?▼

The best way to prevent recurring issues is to analyze per-patch prevention points and tech-stack conventions. This establishes cross-project consistency by tailoring base skills with governance guardrails for your specific projects.

How do I update skill context files with traceable rules based on patch analysis?▼

You update skill context files by running an analysis on your project patches, context, and conventions. The system then delivers concrete improvement rules and writes them directly to the skill-context directory.

Can I use patch analysis to create skill-context overrides for non-aif skills?▼

Yes, patch analysis can evaluate and update non-aif skills. While generated rules are primarily written to specific skill-context directories, the system can optionally update built-in SKILL.md files to apply governance overrides.

Do I need existing project context to evolve installed skills?▼

Yes, existing project context is required. The evolution process depends on analyzing your accumulated patches, codebase patterns, and tech-stack conventions to accurately identify gaps and generate relevant project-specific rules.

Related Skills

Explore More Software Engineering Skills→
batFormatbatFormat

aif-evolve

Analyze project context and patches to improve AI Factory skills.

Community
Advanced
ExsyDevExsyDev

aif-architecture

Generate tailored ARCHITECTURE.md guidelines from project tech stack and context.

Community
Advanced
vulikjulikvulikjulik

aif-evolve

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

Community
Advanced
thimsluggathimslugga

kernel-review

Analyze Linux kernel patch regressions and generate vector payloads for review.

Community
Advanced