repo-harness-migrate

Name: repo-harness-migrate
Availability: InStock
Author: Ancienttwo

Migrate legacy Claude/Codex workflow repositories to the tasks-first harness format.

407|29|Updated Mar 19, 2026

Search Tags:#shell scripting #workflow conversion #repository migration #document preservation #Claude/Codex

Ready to run

npx skills add https://github.com/Ancienttwo/repo-harness --skill repo-harness-migrate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: repo-harness-migrate
Source: https://github.com/Ancienttwo/repo-harness/tree/main/assets/skill-commands/repo-harness-migrate
Command: npx skills add https://github.com/Ancienttwo/repo-harness --skill repo-harness-migrate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you transition older Claude/Codex workflow repositories to the current tasks-first harness, preserving or archiving user-authored documents and hooks.

Core Features & Use Cases

Legacy Workflow Migration: Converts older workflow repositories to the current tasks-first harness format.
Document Preservation: Ensures that user-authored documents and hooks are preserved during the migration process.
Use Case: If you have a repository using the old Claude/Codex workflow and want to update it to the new tasks-first harness without losing any data, use this Skill.

Quick Start

Migrate your legacy Claude/Codex workflow repository to the new harness by running the following command: repo-harness-migrate --repo /path/to/your/repo.

Frequently Asked Questions about repo-harness-migrate

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

FAQPage Schema

How do I migrate a legacy Claude/Codex workflow repository to the tasks-first harness?▼

To migrate a legacy Claude/Codex workflow repository, run the provided shell script with the repository path. This converts the older structure to the current tasks-first harness format.

Does repository migration preserve my user-authored documents and hooks?▼

Yes, repository migration preserves user-authored documents and hooks. The process ensures your existing files and configurations are kept intact or archived during the format conversion.

What is a tasks-first harness and when do I need to convert my repository?▼

A tasks-first harness is the current workflow format replacing older Claude/Codex repository structures. You need to convert when updating legacy setups to maintain compatibility without losing data.

Do I need shell scripting knowledge to run the repository migration?▼

No, you do not need shell scripting knowledge to run the migration. You execute a pre-built shell script via a single command, requiring only repository access to complete the conversion.

Can I use this workflow conversion tool for repositories without shell script execution access?▼

No, you cannot use this workflow conversion tool without shell execution access. The migration requires the ability to run shell scripts directly within the target repository environment.

What is the best way to update old Claude/Codex workflows without losing custom configurations?▼

The best way to update old Claude/Codex workflows is using a dedicated migration script. It specifically targets and preserves your custom configurations and user-authored documents during the transition.