codevolution

Propagate .claude agent, skill, and rule changes to a centralized template.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/naj2r/claude-econ-paper-template --skill codevolution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codevolution
Source: https://github.com/naj2r/claude-econ-paper-template/tree/main/.claude/skills/codevolution
Command: npx skills add https://github.com/naj2r/claude-econ-paper-template --skill codevolution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeping project-specific Claude infrastructure synchronized with a central template is tedious and error-prone; CODEvolution automates evaluation and propagation so maintainers don't have to manually generalize and copy infra files across repositories.

Core Features & Use Cases

  • Automatic Triggering: Runs after creation or substantive modification of files in .claude/agents/, .claude/skills/, or .claude/rules/.
  • Universalization Protocol: Applies a deterministic set of rules to remove study-specific details and replace paths/parameters with generic variables before propagation.
  • Decision Thresholds & Safety: Uses a confidence threshold to decide between automatic propagation, asking the user, or skipping, and prevents recursive triggers.
  • Background Agent Orchestration: Spawns a dedicated CODEvolution subagent to produce the generalized file and produces a concise report of actions taken.
  • Use Case: Maintain a canonical econ-paper-template by automatically propagating generic infra updates from individual project repos while preserving project-specific exceptions.

Quick Start

Ask the orchestrator to run CODEvolution after updating a .claude agent, skill, or rule so it can evaluate, universalize, and propagate the change to the template repository.

Frequently Asked Questions about codevolution

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

FAQPage Schema
How do I auto-sync infrastructure changes to a central template repository?

To auto-sync infrastructure changes, a background agent evaluates modified .claude files, removes project-specific details, and writes the generalized content to your template repository path. It uses confidence thresholds to decide whether to propagate automatically, ask the user, or skip.

What is the best way to propagate .claude agents and rules across multiple repos?

Propagating .claude agents and rules is best handled by a universalization protocol that strips project-specific parameters and replaces them with generic variables before writing generalized files to a centralized template repository, ensuring safe code propagation without manual copying.

How does universalization work when syncing infrastructure files?

Universalization works by applying deterministic rules to remove project-specific details from modified .claude files, replacing paths and parameters with generic variables before writing the generalized file to the template repository path.

Can I run repo-sync as a background agent without triggering recursive loops?

Yes, repo-sync runs as a dedicated background subagent that evaluates changes and produces a report without triggering recursive runs. It spawns specifically to generate generalized files and prevent infinite propagation loops.

When should I not use automated code propagation for template repositories?

You should not use automated code propagation when your .claude file changes contain purely project-specific details that cannot be universalized, or when the background agent's confidence threshold determines the changes should be skipped rather than propagated.