movie-cli-migration-and-optimization

Orchestrates repository migration to .ai-memory architecture and DRY refactoring of Go codebases.

Updated May 16, 2026
One-click install
npx skills add https://github.com/alimtvnetwork/img-pdf-v2 --skill movie-cli-migration-and-optimization-alimtvnetwork
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: movie-cli-migration-and-optimization
Source: https://github.com/alimtvnetwork/img-pdf-v2/tree/main/.agents/skills/movie-cli-migration-and-optimization
Command: npx skills add https://github.com/alimtvnetwork/img-pdf-v2 --skill movie-cli-migration-and-optimization-alimtvnetwork

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Legacy repositories using the .lovable folder structure need to be migrated to the modern .ai-memory and 02-spec architecture, and their Go codebases require DRY optimization such as replacing legacy error wrappers with pkg/appfault and enforcing strict boolean standards. Doing this manually across many files is error-prone and inconsistent. ## Core Features & Use Cases - Repository Migration: Synchronizes .ai-memory, 02-spec, 01-prompts, 03-ai-scripts, and agents.md from a central orchestration repo, migrates .lovable/memory/ into .ai-memory/memory/, and removes legacy folders. - DRY Code Optimization: Spawns execution subagents to replace apperror with appfault, fix boolean flag names, extract embedded options structs, and enforce line length under 100 characters. - Atomic Consolidation: Merges subtask logs into .ai-memory/plans/completed/ and commits all changes in a single atomic git commit. - Use Case: A maintainer of movie-cli-v8 needs to modernize the repo structure and standardize error handling across the Go codebase without running builds or tests during the refactor loop. ## Quick Start Ask the agent to run the movie-cli migration and optimization workflow to migrate the repository structure and refactor the Go codebase with appfault error handling.

Frequently Asked Questions about movie-cli-migration-and-optimization

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

FAQPage Schema
How do I migrate a .lovable repository to the .ai-memory architecture?

Pull the target repository, synchronize .ai-memory, 02-spec, 01-prompts, 03-ai-scripts, and agents.md from the central orchestration repo, then move .lovable/memory/ into .ai-memory/memory/ and delete the legacy .lovable and spec folders.

How do I replace apperror with appfault in a Go codebase?

Spawn execution subagents to refactor the Go code by replacing legacy apperror wrappers with pkg/appfault, fixing boolean flag names, and extracting embedded options structs. Ensure all lines stay under 100 characters during the refactor.

Can I run tests or builds during the migration loop?

No. The workflow explicitly prohibits running tests or build checks during the execution loop. Validation happens outside this process, and all changes are committed in a single atomic git commit at the end.

What happens to existing 02-spec folders during migration?

Existing 02-spec/21-app and 02-spec/22-app-issues directories are moved into their respective target locations under the new 02-spec structure. Legacy spec folders are deleted after the memory content is migrated.

When should I not use this migration workflow?

Avoid this workflow if the repository does not follow the .lovable legacy structure or the central orchestration repo layout. It is purpose-built for movie-cli-v8 style repositories and assumes that specific folder conventions exist.