Eng Cutover Verification
Prove a migration, module split, library swap, datastore or deploy-tool cutover, compatibility removal, or multi-PR cleanup is complete. Use when retiring paths, adapters, dependencies, generated outputs, or config, validating merged main, or proving a rebase preserved a patch series.
Install
npx skills add jpoehnelt/skills --skill eng-cutover-verificationgit clone --depth 1 https://github.com/jpoehnelt/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/eng-cutover-verification ~/.claude/skills/eng-cutover-verificationPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Cutover verification Prove the retired surface is gone, the replacement is adopted, and the integrated build passes. Repo facts (from AGENTS.md or CLAUDE.md): the compatibility promise (whether old paths may coexist and how a retained shim is marked), check and test commands, generated artifacts and how to refresh them, cross-package contracts, the local dev or health endpoints a live check can probe, and who owns deploy and rollback procedures. ## Declare the proof first Before editing, write down: - Retired paths, symbols, imports, dependencies, and config keys that must disappear (for example a removed config file, an old import, a script name). - The replacement and where it is composed (package `exports`, deploy config, a task-runner task). - Focused tests that prove behavior is preserved. For datastore cutovers, include the test harnesses and store unit tests. - Generated artifacts to refresh. Encode the proof with [`scripts/cutover-audit.sh`](scripts/cutover-audit.sh). It is read-only: it searches tracked files and runs only the commands you pass, from the repo root, each bounded by `--timeout` (default 900 seconds).
Details
- Skill name
eng-cutover-verification- Repository
- jpoehnelt/skills
- Path
eng-cutover-verification/SKILL.md- License
- MIT
- Repo updated
- 12 November 2026
FAQ
What does the Eng Cutover Verification skill do?
Prove a migration, module split, library swap, datastore or deploy-tool cutover, compatibility removal, or multi-PR cleanup is complete. Use when retiring paths, adapters, dependencies, generated outputs, or config, validating merged main, or proving a rebase preserved a patch series.
How do I install the Eng Cutover Verification skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jpoehnelt/skills --skill eng-cutover-verification. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Eng Cutover Verification popular?
It lives in jpoehnelt/skills, which has 23 GitHub stars and 1 forks.
Related skills
Agents Correct
23jpoehnelt/skills
Find the mistakes agents keep repeating in a repo and make each one impossible, trying architecture first, then types, lint, tests, and docs last. Use when the operator keeps correcting the same mistake, or for /agents-correct.
Agents Create Verification Skill
23jpoehnelt/skills
Generate a project-local verify skill that drives the app like a user through a browser with Playwright, a CLI, or HTTP. Use for /agents-create-verification-skill, "make a verify skill for this repo", or when a project has no scripted way to prove UI, CLI, or service behavior.
Agents Reflect
23jpoehnelt/skills
After a work session, review what went wrong and right and turn each lesson into a concrete edit to an existing skill or AGENTS.md line. Use when the user says "reflect" or /agents-reflect.
Gh CI Triage
23jpoehnelt/skills
Diagnose failing GitHub Actions CI from log evidence and choose a fix, rerun, merge-forward, or escalation. Use when a PR or default-branch run is red, cancelled, or flaky, or a visual baseline or artifact is missing.
Comms Why
23jpoehnelt/skills
Explain why code is shaped the way it is, using git history, PRs, and connected MCP evidence, with citations and honest confidence. Use for "why does X work this way", "why did we pick Y", design rationale, regressions, and postmortems. Use comms-how for runtime behavior.
Gh PR Commit Review
23jpoehnelt/skills
Review new commits on open GitHub PRs against their actual base without stale or duplicate findings. Use for cutoff-based or scheduled review sweeps, stacked or rebased PRs, cleaning up review threads, or posting actionable inline findings. Read-only except comments and thread resolution.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.