skills.rest
weiping
weipingCOMMUNITY
Explore all skills by this author →
GitHub

migrate

Provide a migration stub for fixture testing of brain migration behavior.

1|Updated May 9, 2026
Search Tags:#migration#regression#skill#brain#openclaw#fixture testing#mixed-merge
One-click install
npx skills add https://github.com/weiping/gbrain-cn --skill migrate-weiping
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migrate
Source: https://github.com/weiping/gbrain-cn/tree/main/test/fixtures/openclaw-mixed-merge/skills/migrate
Command: npx skills add https://github.com/weiping/gbrain-cn --skill migrate-weiping

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a lightweight migration stub used in fixture testing to validate mixed-merge behavior when a “brain” is being migrated.

Core Features & Use Cases

  • Fixture migration stub: Acts as a placeholder for fixture tests without performing real migration logic.
  • Regression test support: Helps ensure versioned migration flows (e.g., v0.40.11.0) behave consistently across mixed-merge scenarios.
  • Use Case: When you are running automated tests for an AI brain repository migration, you can reference this stub to keep the test pipeline focused on merge/migration wiring rather than migration execution.

Quick Start

Use the migrate skill in your fixture test workflow to simulate a “Migrating a brain” step for the openclaw-mixed-merge regression scenario.

Frequently Asked Questions about migrate

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

FAQPage Schema
How do I stub a brain migration step for fixture testing?▼

To stub a brain migration step for fixture testing, use a migration placeholder skill that simulates the process without executing real migration logic, keeping your test pipeline focused on merge wiring.

What is a mixed-merge regression scenario in brain migration?▼

A mixed-merge regression scenario in brain migration occurs when versioned migration flows must behave consistently across merges, requiring a stub to validate that the merge and migration wiring functions correctly.

How do I test brain migration behavior without executing real migration logic?▼

You test brain migration behavior without real execution by using a lightweight migration stub that acts as a placeholder, ensuring the test pipeline validates wiring and regression behavior rather than performing actual migration work.

Does the migration stub support deterministic test activation?▼

Yes, the migration stub supports deterministic test activation by using YAML frontmatter triggers combined with a minimal operational body stub to ensure consistent and predictable test execution.

When do I need a migration placeholder in my automated test workflow?▼

You need a migration placeholder in your automated test workflow when running tests for an AI brain repository migration to ensure the test pipeline remains focused on merge and migration wiring rather than migration execution.

Related Skills

Explore More Software Engineering Skills→
broomvabroomva
3

harness-selftest

Validate evaluation fixture integrity within CI/CD pipelines.

Community
Basic
starlink-awakenstarlink-awaken

skillpack-check

Aggregate gbrain doctor checks and migration statuses into JSON reports.

Community
Intermediate
weipingweiping
1

book-mirror

Mirror and personalize book chapter content for targeted reuse.

Community
Basic
dain-agencydain-agency

migrate-verify

Cross-reference migration manifests with codebase files to verify task completion.

Official
Advanced