Upgrade Framework Version
This loop automates the process of upgrading a project's framework to a newer version. It systematically analyzes the current framework, plans the upgrade path, updates dependencies, resolves breaking changes, and ensures all tests pass before completion.
Goal
Complete framework migration
How to Run
This loop guides you through upgrading your framework version with automated checks. It will incrementally update the framework, handle breaking changes, and verify stability at each step.
- 01
Configure Your Tool
Ensure your coding agent (Cursor, Claude Code, etc.) is set up to accept and process prompts.
- 02
Run the Loop
Execute this loop in your preferred environment. The agent will generate and execute prompts to perform the upgrade.
- 03
Follow Prompts
Respond to each prompt generated by the agent to complete the upgrade process.
Workflow Steps
- 01
Analyze Current Framework
Identify the current framework version and assess its usage in the codebase.
- 02
Plan Upgrade Path
Determine the target framework version and outline necessary steps for migration.
- 03
Update Dependencies
Modify package.json, pom.xml, or other dependency files to reflect the new framework version.
- 04
Address Breaking Changes
Refactor code to accommodate API changes, deprecations, and new patterns introduced in the target version.
- 05
Test and Validate
Run the full test suite to ensure the application works correctly with the upgraded framework.
- 06
Resolve Issues
Fix any failing tests or compatibility issues identified during validation.
Kickoff Prompt
Start the "Upgrade Framework Version" loop. Goal: Complete framework migration Max iterations: 10 Between iterations run: build and test Exit when: Build and tests pass Begin by checking the current framework version and dependencies. Analyze the codebase to identify potential breaking changes that may occur during the upgrade. Generate a plan for migrating to the target framework version while preserving existing functionality. Self-pace this loop. After each iteration, run `build and test` and evaluate the output, and only continue if the exit condition is not met (Build and tests pass). Stop when the exit condition passes or 10 iterations are reached. Give a short status update each pass.
Guardrails
hardcoded- ·Do not introduce breaking changes without addressing them explicitly
- ·Ensure all dependencies are compatible with the target framework version
- ·Preserve existing application functionality during the upgrade
- ·Validate that all tests pass before proceeding to the next step
- ·Document any configuration changes made during the migration
Flow Diagram
Related loops — Maintenance
Maintenance
Package Audit Fixer
Automatically identifies and fixes package vulnerabilities in your Node.js project by running `npm audit` and applying recommended fixes until the audit is clean.
Maintenance
Dependency Update Until Green
Automated loop to safely upgrade project dependencies while ensuring all tests pass after each update. The agent incrementally updates out-of-date packages and runs test checks to prevent breaking changes.
Maintenance
Monorepo Health Check
This loop performs a comprehensive health check of a monorepo by validating its structure, dependencies, code quality, and consistency. It iteratively identifies and resolves issues related to missing dependencies, outdated packages, lint errors, and architectural inconsistencies until the repository passes validation.