SkillVaultskills Browse all 1,000+ skills

Maintenance · Version 1.1.0 · Reviewed 2026-08-02

GitHub Actions Migration Planning Specialist

Reduce change risk for GitHub Actions compatibility inventory and GitHub Actions incremental migration sequence with evidence, explicit trade-offs, and a verification plan.

4 method steps 6 documented failure modes 5 diagnostic checks 7 quality gates

Sequences compatibility, data, and rollout work into reversible migrations for GitHub Actions using workflow YAML, action references, permissions, environments, and artifacts and job timing, cache hits, permission grants, and artifact provenance, with explicit attention to untrusted input or mutable action references gaining write-capable repository credentials.

₹199 one-time

Get this skill archive

Install in your AI coding tool

SkillVault packages this skill in the open Agent Skills format for five leading coding tools.

What this skill helps you do

  • GitHub Actions compatibility inventory
  • GitHub Actions incremental migration sequence
  • GitHub Actions rollback rehearsal

How GitHub Actions Migration Planning Specialist works

You provide

Current state, consumer inventory, and target state

It inspects

Coexistence and rollback viability for GitHub Actions compatibility inventory

It decides

A GitHub Actions incremental migration sequence sequence in reversible increments

You verify

Shadow comparison reports divergence rather than assuming zero

What it checks first

GitHub Actions Migration Planning Specialist sequences compatibility, data, and rollout work into reversible migrations for GitHub Actions using workflow YAML, action references, permissions, environments, and artifacts and job timing, cache hits, permission grants, and artifact provenance, with explicit attention to untrusted input or mutable action references gaining write-capable repository credentials. Use it when the work involves GitHub Actions compatibility inventory, GitHub Actions incremental migration sequence, GitHub Actions rollback rehearsal.

  1. Whether the old and new paths can coexist, which determines if incremental migration is possible at all.
  2. The true consumer inventory, including internal jobs, scripts, and integrations not visible in the main codebase.
  3. Data volume and the time the migration takes at production scale, not sample scale.
  4. Whether the change is backward compatible for data written by the previous version during rollout.
  5. The rollback path, and specifically whether it remains available after the first irreversible step.

Failure modes it recognizes

  • A migration validated on a sample that takes hours on production volume and holds a lock throughout.
  • Dual-write divergence where one write succeeds and the other fails, with no reconciliation.
  • A backfill that races with live writes and overwrites newer values with older ones.
  • Removing the old path before all consumers migrated, discovered by a quarterly batch job weeks later.
  • A schema change that is forward compatible but not backward compatible, blocking rollback.
  • Enum or type widening that older readers cannot parse, breaking during a partial rollout.

Answers it will reject

  • A big-bang cutover with a maintenance window, which concentrates all risk into one unrehearsed moment.
  • Migrating and refactoring simultaneously, which makes failures impossible to attribute.
  • Treating the migration as done at cutover rather than after the old path is removed and verified unused.
  • Skipping the shadow-read comparison because the new implementation "obviously" matches.

Decision rules it applies

  • Use expand-migrate-contract: add the new shape, write both, migrate readers, then remove the old shape.
  • Every increment must be independently verifiable and independently revertible.
  • Keep the old path observable until traffic proves equivalence; remove it only on evidence of zero use.
  • Prefer additive schema changes; a removal is a separate, later, deliberately scheduled change.

Evidence it asks for

  • Run shadow reads comparing old and new outputs, and report the divergence rate rather than assuming zero.
  • Instrument usage of the deprecated path with a caller identifier so removal can be proven safe.
  • Rehearse the migration on a production-sized copy and record the actual duration and lock behavior.

The method inside

  1. Inventory dependencies, compatibility constraints, and current behavior affecting GitHub Actions compatibility inventory.
  2. Create reversible seams for GitHub Actions incremental migration sequence before changing the critical path.
  3. Sequence GitHub Actions rollback rehearsal into independently verifiable increments with explicit rollback points.
  4. Keep old and new paths observable until equivalence is proven; remove the fallback only after acceptance criteria pass.

Deliverables

  • GitHub Actions compatibility inventory assessment
  • GitHub Actions incremental migration sequence decision and action plan
  • GitHub Actions rollback rehearsal verification checklist

Evidence requirements

  • Current and target versions
  • Dependency graph and changelogs
  • Tests, compatibility constraints, and rollout environment

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Apply the migration planning specialist to our GitHub Actions system before the next production change. We can provide workflow YAML, action references, permissions, environments, and artifacts; the main concern is untrusted input or mutable action references gaining write-capable repository credentials.

Expected output

Inventory consumers of workflow YAML, action references, permissions, environments, and artifacts before selecting the cutover. The migration must explicitly contain untrusted input or mutable action references gaining write-capable repository credentials. Introduce a coexistence boundary, compare old and new behavior on the same workload, and rehearse rollback before removing the legacy path.

Boundaries and compatibility

Ideal for

  • GitHub Actions compatibility inventory: produce a decision or artifact grounded in supplied evidence.
  • GitHub Actions incremental migration sequence: produce a decision or artifact grounded in supplied evidence.
  • GitHub Actions rollback rehearsal: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Blindly upgrading across multiple major versions
  • Assuming semantic versioning guarantees compatibility

Agent compatibility

  • GitHub Copilot Agent Skills
  • Cursor Agent Skills
  • Claude Code Skills
  • OpenAI Codex Skills
  • JetBrains Junie Skills

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.