claudecodex

ai-migration-kit

Transition entry for installs made before the rename to tagout (#611, #618): the whole kit under its old name, from the root's transition manifest, so `ai-migration-kit@ai-migration-kit-marketplace` keeps loading. Reinstall as tagout@tagout-marketplace (+ tagout-migrate for .NET); this entry and the root manifest go away with the 3.0.0 release (#610).

4 on GitHubby Philippe Matrayv4.2.0MITupdated yesterdayCoding
/

Plugin ai-migration-kit from marketplace tagout-marketplace in phmatray/tagout. Commands read from the repo's manifest — yesterday.

This plugin runs code on your machine — it starts local MCP servers. The exact commands are listed below; read them before installing.

What it installs

Skills (12)

  • auto-dev

    Burn down a GitHub issue backlog hands-off with a FLEET of N parallel workers — each drives one issue through `implement-issue` → `merge-pr`, then takes the next, so N stay in flight. The orchestrator ABOVE those skills: ordering, NON-overlapping areas per worker, CI waits, verified merge state (wor

  • create-issue

    Create a fully-seeded GitHub issue — not a bare `issue-create` call: template-compliant, carrying a brainstorm → spec → implementation-plan trail so a contributor can pick it up cold. ALWAYS reach for this whenever the user wants to open, file, add, raise, log, or track a NEW issue / feature request

  • create-pr

    Open a pull request for a finished feature branch — or a fix left on the default branch itself (debug-issue's hand-off), which this skill branches off first: push it through the guard, link its issue, gate the title, and open it ready when the full test passes (a draft when asked, or when the test i

  • debug-issue

    Use the moment a user reports something broken or behaving unexpectedly — a bug, failing or flaky test, crash, exception, stack trace, regression, build break, or integration failure — and use it BEFORE the first command you would run to investigate, not just before the fix. That first look is where

  • deliver-issue

    Take ONE idea or ONE planned issue all the way to a merged PR, hands-off — file or seed it with create-issue, build it with implement-issue, land it with merge-pr, each phase in a FRESH sub-agent context. Use when the user wants the whole chain run for a single item: "deliver issue 47 end to end", "

  • implement-issue

    Turn an existing GitHub issue into a finished pull request — the actual coding. Use when an issue carries a `🛠️ Implementation plan` checklist and the user wants it BUILT: worktree, draft PR, task-by-task commits ticked on the live issue, review, ready-flip. Triggers: "implement issue 47", "knock o

  • init

    Make a repository ready for the issue/PR lifecycle skills in one command — record its facts in the committed profile (`.claude/skills/repo-profile.md`: commit identity, build/test commands, labels, merge style, conflict hot-spots), converge its labels, issue forms, settings, topics and Pages source

  • merge-pr

    Land an open GitHub pull request. Use whenever the user wants to MERGE, land, ship, or close out an open PR: waits for CI, applies corrections until mergeable (red checks, conflicts with the latest `main`, unresolved review), squash-merges, triages follow-ups, and tears down the branch and worktree.

  • migrate-legacy

    Use when upgrading, migrating, or modernizing a legacy application — outdated target framework, out-of-support runtime, obsolete APIs, old packages, or legacy idioms. Triggers on "upgrade this app", "migrate to .NET 10", "modernize this codebase", "this project targets an old framework", « mets à ni

  • review-followups

    Consolide et met à jour les suivis ouverts des migrations (next_steps/deferred des migration/report.json + backlog du kit). Use whenever the user asks what remains open across migrated repos, wants a status of pending decisions, says a follow-up item is done, or decides to close/abandon one — trigge

  • review-sessions

    Read the transcripts of PREVIOUS sessions and pull out the failures the kit itself caused — errors on kit scripts, gate denials, workers that died waiting, red kit suites — then cluster them by root cause, drop what main already fixed, and file what earns an issue through create-issue. Use when the

  • triage-backlog

    Prune and re-decide an EXISTING GitHub issue backlog: verifies which open issues are already fixed or superseded, clusters the rest by root cause, proposes ONE disposition each and executes only what the owner confirms. ALWAYS reach for this when the user wants to prune, triage, groom, re-decide, or

Slash commands (7)

  • /ai-migration-kit:auto-dev-merge

    PHASE 2 of an auto-dev worker — land the already-ready PR via merge-pr, in a fresh context. Dispatched by the supervisor; `/auto-dev-merge <pr-number>`.

  • /ai-migration-kit:auto-dev-worker

    PHASE 1 of an auto-dev worker — implement-issue up to a ready PR, then stop so a fresh sub-agent merges it. Dispatched by the supervisor; `/auto-dev-worker <issue-number>`.

  • /ai-migration-kit:migrate-assess

    Read-only legacy audit — inventory, diagnostics, risk map, recommended target (no code changes)

  • /ai-migration-kit:migrate-audit

    Read-only executive audit — costed effort, risks, recommended target; multiple apps → portfolio synthesis

  • /ai-migration-kit:migrate-followups

    Consolidate the migrated repos' open follow-ups (owner decisions, tasks, deferrals) and update them at the source

  • /ai-migration-kit:migrate-verify

    Re-runnable final quality gate for a migrated app — clean build, tests, diagnostics vs baseline, report

  • /ai-migration-kit:migrate

    Run the full seven-phase legacy upgrade pipeline (assess → verified production) powered by RoselineMCP

MCP servers (2)

  • roseline

    runs: dnx RoselineMCP --yes

  • adr

    runs: dnx AdrMcp --yes

View source on GitHub phmatray.github.io

More from phmatray/tagout

All 3 plugins →

tagout

claudecodex

The gate-verified GitHub issue → pull request lifecycle for coding agents: create-issue, implement-issue, merge-pr, auto-dev, triage-backlog and their guards. No bundled MCP server, no .NET prerequisite. Add tagout-migrate for a legacy .NET application.

10 skills · 2 commands

4

The gate-verified seven-phase pipeline that takes a legacy .NET application to verified production, powered by RoselineMCP (Roslyn). Ships the roseline Read gate and the roseline + adr MCP servers (dnx, .NET 10 SDK). Install beside tagout.

2 skills · 5 commands · 2 MCP servers

4

Similar plugins

Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).

39 skills

mattpocock/skills 323,108

superpowers

claudecodex

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

obra/superpowers 316,836

claude-mem

claudecodex

Persistent memory for Claude Code: the next session starts where the last one left off.

29 skills · 1 MCP server · hooks

thedotmack/claude-mem 116,618

career-ops

claudecodex

Open-source AI job search that runs locally in your AI coding CLI: scan job portals, evaluate listings into a structured A-H report with a 1-5 score, tailor your CV, track applications

5 skills · hooks

career-ops-hq/career-ops 82,253

mem0

claudecodex

Cross-session memory and token savings for coding agents.

6 skills · 1 agent · 1 MCP server · hooks

mem0ai/mem0 68,893

context7

claudecodex

Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.

1 MCP server

upstash/context7 64,709

Maintain ai-migration-kit?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins3 plugins