upgrade-cleanup

Name: upgrade-cleanup
Author: ombulabs

368stars13forks

How to install upgrade-cleanup?

ombulabs/claude-code_rails-upgrade-skill/upgrade-cleanup

$npx -y skills add ombulabs/claude-code_rails-upgrade-skill --skill upgrade-cleanup

Installs into the current project.

Summary

Clean up after (or abandon) a Rails upgrade. Drop NextRails.next? and NextRails.current? branches and retire dual-boot scaffolding (Gemfile.next, Gemfile.next.lock, conditional Gemfile groups), keeping either the next or the current version. Trigger when the user says they are do

Files · 1

View on GitHub

SKILL.md

1	# Upgrade Cleanup Skill
2
3	Companion to the `rails-upgrade` plugin. Runs the cleanup pass that removes dual-boot scaffolding and aligns the codebase to the new version baseline.
4
5	When activated, follow the workflow in `workflows/upgrade-cleanup-workflow.md` end-to-end. Before any destructive step, confirm direction with the user (Phase 0 Step 1): are they keeping the next version (finishing the upgrade) or keeping the current version (abandoning or pausing this hop)? Every subsequent step branches on that answer. To detect the next version, read the `Gemfile` (look for the `if NextRails.next?` / `else` block; the `next?` branch holds the upgraded-to version) or `Gemfile.next.lock`. Do NOT rely on `Gemfile.lock` alone, since during dual-boot it still pins the current version.
6
7	## When to Run
8
9	Run when the user has explicitly decided to end the dual-boot phase in one of two directions:
10
11	- Keep next: upgrade is done (final hop or stopping point), drop the `else` / current branches.
12	- Keep current: abandoning or pausing this hop, drop the `if NextRails.next?` / next branches and `Gemfile.next*`.
13
14	Either way the previous parallel branch must no longer be needed (no rollback window). Deployment to production is not a hard prerequisite.
15
16	## Ownership and Delegations
17
18	This skill owns the cleanup. Phase 1 below is the step list to follow. The `dual-boot` skill's `workflows/cleanup-workflow.md` is older optional reading; if it drifts from this workflow, this workflow wins.
19
20	- Dual-boot scaffolding removal: performed here in Phase 1.
21	- `load_defaults` alignment: out of scope. The `rails-upgrade` skill handles this via its `rails-load-defaults` step before cleanup runs.
22
23	## Critical Rules
24
25	- Do NOT leave `NextRails.next?` or `NextRails.current?` branches in the tree. That is the failure mode this skill exists to prevent.
26	- Do NOT start removing branches before confirming direction. Keeping the wrong side throws away the work the user wants to keep. If the user has not stated next vs current, ask.
27
28	## Workflow
29
30	See `workflows/upgrade-cleanup-workflow.md` for the full process: a pre-flight check, dual-boot scaffolding removal, old-version code retirement, CI and Ruby pin alignment, final verification, and the cleanup PR.
31
32	## Reference
33
34	- [Finishing an Upgrade, FastRuby.io](https://www.fastruby.io/blog/finishing-an-upgrade.html)
35	- `workflows/upgrade-cleanup-workflow.md`, full workflow
36	- The `dual-boot` plugin's `workflows/cleanup-workflow.md`, optional reading for context. This skill's Phase 1 is the step list to follow, do not use dual-boot's version when it conflicts.

People who liked this also viewed

6 picks

Type

upgrade-cleanup

368stars13forks

View on GitHub

How to install upgrade-cleanup?

ombulabs/claude-code_rails-upgrade-skill/upgrade-cleanup

$npx -y skills add ombulabs/claude-code_rails-upgrade-skill --skill upgrade-cleanup

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Upgrade Cleanup Skill
2
3	Companion to the `rails-upgrade` plugin. Runs the cleanup pass that removes dual-boot scaffolding and aligns the codebase to the new version baseline.
4
5	When activated, follow the workflow in `workflows/upgrade-cleanup-workflow.md` end-to-end. Before any destructive step, confirm direction with the user (Phase 0 Step 1): are they keeping the next version (finishing the upgrade) or keeping the current version (abandoning or pausing this hop)? Every subsequent step branches on that answer. To detect the next version, read the `Gemfile` (look for the `if NextRails.next?` / `else` block; the `next?` branch holds the upgraded-to version) or `Gemfile.next.lock`. Do NOT rely on `Gemfile.lock` alone, since during dual-boot it still pins the current version.
6
7	## When to Run
8
9	Run when the user has explicitly decided to end the dual-boot phase in one of two directions:
10
11	- Keep next: upgrade is done (final hop or stopping point), drop the `else` / current branches.
12	- Keep current: abandoning or pausing this hop, drop the `if NextRails.next?` / next branches and `Gemfile.next*`.
13
14	Either way the previous parallel branch must no longer be needed (no rollback window). Deployment to production is not a hard prerequisite.
15
16	## Ownership and Delegations
17
18	This skill owns the cleanup. Phase 1 below is the step list to follow. The `dual-boot` skill's `workflows/cleanup-workflow.md` is older optional reading; if it drifts from this workflow, this workflow wins.
19
20	- Dual-boot scaffolding removal: performed here in Phase 1.
21	- `load_defaults` alignment: out of scope. The `rails-upgrade` skill handles this via its `rails-load-defaults` step before cleanup runs.
22
23	## Critical Rules
24
25	- Do NOT leave `NextRails.next?` or `NextRails.current?` branches in the tree. That is the failure mode this skill exists to prevent.
26	- Do NOT start removing branches before confirming direction. Keeping the wrong side throws away the work the user wants to keep. If the user has not stated next vs current, ask.
27
28	## Workflow
29
30	See `workflows/upgrade-cleanup-workflow.md` for the full process: a pre-flight check, dual-boot scaffolding removal, old-version code retirement, CI and Ruby pin alignment, final verification, and the cleanup PR.
31
32	## Reference
33
34	- [Finishing an Upgrade, FastRuby.io](https://www.fastruby.io/blog/finishing-an-upgrade.html)
35	- `workflows/upgrade-cleanup-workflow.md`, full workflow
36	- The `dual-boot` plugin's `workflows/cleanup-workflow.md`, optional reading for context. This skill's Phase 1 is the step list to follow, do not use dual-boot's version when it conflicts.

People who liked this also viewed

6 picks

Type