skills.rest
quanpersie2001
quanpersie2001COMMUNITY
Explore all skills by this author →
GitHub

v2-to-v3-migration

Detect legacy Pulse v2 layouts and apply approval-gated migration scripts.

Updated Mar 27, 2026
Search Tags:#onboarding#migration#nodejs#non-destructive#pulse#preservation#repo-migration
One-click install
npx skills add https://github.com/quanpersie2001/pulse --skill v2-to-v3-migration
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: v2-to-v3-migration
Source: https://github.com/quanpersie2001/pulse/tree/main/plugins/pulse/skills/v2-to-v3-migration
Command: npx skills add https://github.com/quanpersie2001/pulse --skill v2-to-v3-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

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.

Frequently Asked Questions about v2-to-v3-migration

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

FAQPage Schema
How do I safely migrate a legacy repository layout to the v3 structure without losing data?▼

To safely migrate a legacy repository layout to the v3 structure, run a non-destructive, approval-gated check first to identify stale artifacts. This preserves existing AGENTS content, .pulse data, and unmanaged prompts while applying Node.js 18+ migration scripts only after explicit human approval.

What is the best way to detect stale Pulse v2 artifacts during onboarding?▼

Detecting stale Pulse v2 artifacts during onboarding involves running read-only diagnostics that scan for legacy Python hooks, older plugin versions, and missing v3 support files. This check gathers legacy signals without modifying your repository before you approve any changes.

Does the Pulse v2 to v3 migration process overwrite custom prompts or local state?▼

The Pulse v2 to v3 migration process does not overwrite custom prompts or local state. It performs non-destructive checks and preserves unrelated hooks and existing .pulse memory, queuing semantic normalization tasks for migrated learning memory instead of automatically altering them.

Can I use this migration approach for repositories with partial pre-3.0 installs?▼

Yes, you can use this migration approach for repositories with partial pre-3.0 installs. The process detects incomplete installations and legacy traces, providing a controlled apply workflow that safely upgrades the repository to the v3 layout while preventing accidental data loss.

Do I need Node.js 18+ to run the Pulse v3 migration scripts?▼

Yes, you need Node.js 18+ to run the Pulse v3 migration scripts. The migration process relies on Node.js 18+ based scripts to perform the structural transformation from the legacy v2 layout to the current v3 repository format.

Why should I run a preflight check before applying repository migration changes?▼

Running a preflight check before applying repository migration changes ensures you review a deterministic migration summary and required approvals. This approval-gated step prevents accidental overwrites of custom configurations and confirms exactly what the migration will alter before execution.

Related Skills

Explore More Software Engineering Skills→
mazenyassergithubmazenyassergithub
6

doctor

Diagnoses and fixes oh-my-claudecode installation issues by checking plugin versions, legacy configurations, CLAUDE.md, and stale caches.

Community
Intermediate
thompson0012thompson0012
28

compound-capture

Extract durable lessons from sprint outcomes with artifact path provenance.

Community
Advanced
onelee85onelee85

gsd-health

Validate and repair inconsistencies in the .planning/ directory.

Community
Advanced
comolcomol
413

1c-mxl-validate

Detect structural errors in 1C MXL Template.xml files.

Community
Advanced