unikit-evolve

Analyze patches to propose coding and workflow rules for RULES.md and skill-context.

16|1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/NintendaDev/unikit-ai --skill unikit-evolve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unikit-evolve
Source: https://github.com/NintendaDev/unikit-ai/tree/main/skills/unikit-evolve
Command: npx skills add https://github.com/NintendaDev/unikit-ai --skill unikit-evolve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify concrete prevention points from patches and propose new coding and workflow rules for RULES.md and skill-context, helping teams codify best practices and automate governance.

Core Features & Use Cases

  • Patch analysis to extract prevention points from past mistakes.
  • Classification of each point into coding rules (RULES.md) or workflow rules (skill-context).
  • Cross-check against existing RULES.md and knowledge base, surfacing only uncovered candidates.
  • Evolution logging, cursor management, and safe, reversible rule migration.
  • Supports eventual migration of mature rules to core memory and per-skill contexts.

Quick Start

Invoke /unikit-evolve in your project to analyze patches and generate coding and workflow rules.

Frequently Asked Questions about unikit-evolve

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

FAQPage Schema
How do I extract coding rules from past patches automatically?

Workflow rule generation analyzes patches to identify concrete prevention points and proposes new workflow rules. It cross-checks candidates against existing skill-context files before surfacing them for approval.

What is the best way to prevent duplicate coding rules in a knowledge base?

Cross-checking against existing rules prevents duplicate coding rules in a knowledge base. The system surfaces only uncovered prevention point candidates, ensuring no redundant entries are created in your governance files.

How do I migrate mature rules to core memory safely?

Safe rule migration moves mature coding and workflow rules to core memory only after explicit user confirmation. The process supports cursor management and ensures all migrated rules remain reversible and traceable.

Can I trace proposed coding rules back to their source patches?

Proposed coding rules are strictly traceable to their source patches. The system links every newly generated prevention point back to the exact patch data it was derived from during the analysis phase.