shinka-convert

Convert an existing codebase into a Shinka task with snapshot and evaluation scaffold.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/2233admin/ShinkaEvolve-fork --skill shinka-convert-2233admin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shinka-convert
Source: https://github.com/2233admin/ShinkaEvolve-fork/tree/main/skills/shinka-convert
Command: npx skills add https://github.com/2233admin/ShinkaEvolve-fork --skill shinka-convert-2233admin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires PyYAML, and includes scripts (resource) components.

What problem does it solve?

This skill converts an existing codebase in the current working directory into a Shinka-ready task directory by snapshotting relevant code, adding EVOLVE blocks, and generating evaluate.py plus Shinka runner/config files to enable evolution of existing code with Shinka instead of starting from scratch.

Core Features & Use Cases

  • Converts an existing project into a complete Shinka task scaffold, including evaluate.py, run_evo.py, and shinka.yaml.
  • Generates a minimal yet runnable snapshot of the codebase, preserving behavior outside EVOLVE regions.
  • Supports easy handoff to shinka-run for controlled evolution and measurable metrics.

Quick Start

Convert your current project into a Shinka-ready task directory with minimal setup.

Frequently Asked Questions about shinka-convert

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

FAQPage Schema
How do I convert an existing Python codebase into an evolution task?

To convert an existing Python codebase into an evolution task, this tool snapshots your current working directory and generates a Shinka-ready scaffold with initial.py, evaluate.py, run_evo.py, and shinka.yaml.

Can I evolve an existing project with Shinka instead of starting from scratch?

You can evolve an existing project with Shinka instead of starting from scratch by snapshotting relevant code and injecting EVOLVE blocks to enable measurable code evolution.

What files are generated when converting a repository for codebase evolution?

Converting a repository for codebase evolution generates an evaluate.py script, a run_evo.py runner, and a shinka.yaml configuration file to establish an EVOLVE-BLOCK workflow.

Do I need PyYAML to generate a Shinka task scaffold from my current repository?

You need PyYAML installed to generate a Shinka task scaffold from your current repository, as the conversion process relies on this dependency to parse and output configuration files.

What is the best way to prepare a codebase snapshot for controlled evolution?

The best way to prepare a codebase snapshot for controlled evolution is to preserve behavior outside EVOLVE regions while generating a minimal runnable snapshot ready for shinka-run.

Are there limitations when adding EVOLVE blocks to an existing codebase?

A limitation when adding EVOLVE blocks to an existing codebase is that the generated snapshot preserves behavior strictly outside EVOLVE regions, requiring careful boundary definition for targeted optimization.