Openclaw Migration

What This Skill Does

The OpenClaw Migration skill is a structured utility designed to guide developers and AI agents through the rebranding process of the Clawd project to OpenClaw. This skill provides a comprehensive, step-by-step playbook that ensures the structural, configurational, and documentation-related changes required for such a major transition are executed consistently. By acting as a central source of truth for the migration workflow, it reduces the risk of broken builds, missing dependencies, or inconsistent branding across the codebase.

Installation

To integrate this skill into your development agent, run the following command within your terminal environment: clawhub install openclaw/skills/skills/chenyuan99/openclaw-migration Once installed, the migration playbook will be accessible to your agent, providing the necessary logic to execute and verify the renaming process throughout your repository.

Use Cases

• Project Rebranding: Essential when transitioning the existing clawdbot codebase into the new openclaw structure.
• Dependency Verification: Use this to confirm that pnpm-workspace.yaml, package.json, and tsconfig paths are correctly updated to reflect the new directory layout.
• Contributor Onboarding: Provides a standardized checklist for new developers to understand the project history and the new naming conventions.
• Refactoring Automation: Helps in identifying and mass-updating hardcoded file paths and documentation references that mention the legacy project name.

Example Prompts

1. "I'm starting the transition from Clawd to OpenClaw. What are the first three steps I need to perform to reorganize the directories?"
2. "Can you perform a check on my configuration files to see if any references to 'Clawd' still exist in the CI/CD workflows?"
3. "Please generate a summary report of all file movements made during the OpenClaw migration for my status update to Ivan."

Tips & Limitations

• Safety First: Always perform a full repository backup or create a fresh feature branch before executing bulk renames or moving critical application directories.
• Scope: This skill is specifically tailored for the Clawd to OpenClaw transition. While the patterns can be adapted for other renames, its primary logic relies on the specific structural assumptions of the OpenClaw codebase.
• CI/CD Impact: Be prepared for potential failures in CI pipelines after renaming; ensure your deployment configs (e.g., Fly/Render) are updated in tandem with the file system moves.
• Review: Use the included playbook as a checklist during pull request reviews to ensure all team members adhere to the established migration standards.