loading
loading
Plan a framework upgrade from current docs — breaking-change checklist, file impact, and verify commands.
Reads the target version's actual changelog instead of trusting training-data memory — the difference between a clean upgrade and a broken build.
Listed for review
No verified public repo for this skill yet, so this page does not give you an install command. Skills with a verified source install in one command — or fully manual: copy the skill folder into .claude/skills/ and your agent picks it up.
Boostor Quality Score
84/100 · B
Framework Upgrade Planner builds a real upgrade plan for Next.js, React, Rails, Django, Laravel, and similar frameworks. It reads your package files and the target version's official docs and changelog, then produces the current and target versions, a breaking-change checklist grounded in the migration notes, the files each change touches, and the commands to verify after. It refuses to lean on stale training-data assumptions, because that is exactly how forced upgrades break a build.
Analyze and cut GitHub Actions spend by rewriting slow, expensive workflows.
Aimed at the one bill teams forget to read — it profiles your Actions YAML against real billing data and estimates the savings before touching anything.
Transparent + deterministic: every point above is computed from this skill's real fields plus a prompt-injection safety scan. No black box, no pay-to-rank.
Find the first real failure in a CI log and return the owner, fix path, and rerun command.
Points at the first failing command, not the loudest warning — and stops the agent from editing before it has even read the error.
Create, document, and clean up feature flags across your codebase safely.
Solves flag debt: it tracks every flag and tells you which are safe to delete, then strips the dead branches — so old flags stop rotting in your codebase.