skills.rest
dudusoar
dudusoarCOMMUNITY
Explore all skills by this author →
GitHub

update-migration-log

Record migration entries to MIGRATION_LOG.md using a standardized template.

Updated Apr 23, 2024
Search Tags:#template#documentation#migration#log#audit-trail#MIGRATION_LOG.md
One-click install
npx skills add https://github.com/dudusoar/VRP-Toolkit --skill update-migration-log
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-migration-log
Source: https://github.com/dudusoar/VRP-Toolkit/tree/main/.claude/skills/update-migration-log
Command: npx skills add https://github.com/dudusoar/VRP-Toolkit --skill update-migration-log

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams maintain a clear, auditable record of file migrations by documenting essential details and outcomes in MIGRATION_LOG.md, reducing ambiguity and enabling accurate retrospectives.

Core Features & Use Cases

  • Standardized migration entries: Uses a consistent template to capture original file, destination, status, time spent, and complexity.
  • Audit-ready history: Produces a complete migration history that supports traceability and onboarding.
  • Scope control: Ensures only MIGRATION_LOG.md is modified, leaving CLAUDE.md and TASK_BOARD.md intact.

Quick Start

Add a new migration entry by following the Migration Entry Template and fill in Source, Destination, Status, Time Spent, Complexity, and a concise migration summary before saving to MIGRATION_LOG.md.

Frequently Asked Questions about update-migration-log

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

FAQPage Schema
How do I document file migration activities for an audit trail?▼

To document file migration activities, record detailed entries in a MIGRATION_LOG.md file. This preserves an auditable history of changes, issues, and resolutions for accurate retrospectives.

What should be included in a standardized migration log entry?▼

A standardized migration log entry includes the original source file, destination, status, time spent, complexity, and a concise migration summary, ensuring consistent documentation across teams.

How do I record post-migration changes without affecting CLAUDE.md?▼

Record post-migration changes by appending entries exclusively to MIGRATION_LOG.md. This scope control ensures CLAUDE.md and TASK_BOARD.md remain intact and unmodified.

When do I need a MIGRATION_LOG.md file?▼

You need a MIGRATION_LOG.md file during post-migration tasks across work streams to capture an auditable history of changes, reduce ambiguity, and support onboarding.

What is the best way to maintain traceability for file migrations?▼

The best way to maintain traceability is using a consistent template to capture migration details in MIGRATION_LOG.md, producing a complete history that supports tracking and onboarding.

What are the limitations of using MIGRATION_LOG.md for documentation?▼

The limitation is strict scope control: only MIGRATION_LOG.md is modified. You cannot simultaneously update CLAUDE.md or TASK_BOARD.md while logging migration activities.

Related Skills

Explore More Content & Communication Skills→
jholhewresjholhewres
3

time-tracker

Track task time with start/stop logging and daily CSV reports.

Community
Intermediate
forbotsakeforbotsake
5

learn

Aggregate and index project learnings across sessions in JSONL stores.

Official
Advanced
dudusoardudusoar

update-task-board

Update TASK_BOARD.md by analyzing MIGRATION_LOG.md, DEBUG_LOG.md, and GIT_LOG.md.

Community
Basic
peopledearpeopledear
1

Backend Migrations

Enforce standardized migration practices for backend migration scripts.

Official
Basic