v2-to-v3-migration
CommunitySafely migrate Pulse installs to v3.
Authorquanpersie2001
Version1.0.0
Installs0
System Documentation
What problem does it solve?
This Skill provides a safe, approval-gated wrapper to detect and migrate repositories that contain legacy Pulse v2 traces, legacy Python hooks, or partial pre-3.0 installs so teams can upgrade to the v3 layout without accidental data loss.
Core Features & Use Cases
- Non-destructive checks: Run read-only diagnostics that identify legacy hooks, stale plugin versions, and missing v3 support files.
- Controlled apply workflow: Produce an explicit, approval-gated apply step that performs migration actions and reports a deterministic migration summary.
- Preservation and normalization: Preserve AGENTS content, unrelated hooks, and existing .pulse memory while queuing semantic normalization tasks for migrated learning memory and critical patterns.
- Use Case: When preflight or onboarding surfaces legacy Pulse artifacts, run the check to gather legacy_signals and only run apply after human approval to avoid overwriting custom prompts or local Pulse state.
Quick Start
Run a migration check on the repository, summarize legacy signals and required approvals, and request permission before applying changes.
Dependency Matrix
Required Modules
None requiredComponents
scriptsreferences
💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: v2-to-v3-migration Download link: https://github.com/quanpersie2001/pulse/archive/main.zip#v2-to-v3-migration Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.