Skip to content

Robertjam954/multimodal_rag_application / .claude/skills/azure-upgrade

azure-upgrade

Unverified

Assess and upgrade Azure workloads between plans, tiers, or SKUs, or modernize Azure SDK dependencies in source code. WHEN: upgrade Consumption to Flex Consumption, upgrade Azure Functions plan, change hosting plan, function app SKU, migrate App Service to Container Apps, modernize legacy Azure Java SDKs (com.microsoft.azure to com.azure), migrate Azure Cache for Redis (ACR/ACRE) to Azure Managed Redis (AMR).

FileKindSize
SKILL.mdskill md6.0 KB
references/global-rules.mdmarkdown2.0 KB
references/languages/java/INSTRUCTION.mdmarkdown11.3 KB
references/languages/java/README.mdmarkdown3.0 KB
references/languages/java/bom-migration/bom-gradle-settings.mdmarkdown6.7 KB
references/languages/java/bom-migration/bom-gradle-toml.mdmarkdown2.7 KB
references/languages/java/bom-migration/bom-gradle.mdmarkdown5.1 KB
references/languages/java/bom-migration/bom-maven.mdmarkdown4.7 KB
references/languages/java/bom-migration/bom-migration.mdmarkdown4.2 KB
references/languages/java/bom-migration/bom-validation.mdmarkdown1.5 KB
references/languages/java/package-specific/com.microsoft.azure.eventprocessorhost.mdmarkdown5.5 KB
references/languages/java/package-specific/com.microsoft.azure.management.mdmarkdown9.5 KB
references/languages/java/rules/efficiency.mdmarkdown265 B
references/languages/java/rules/execution-guidelines.mdmarkdown1.0 KB
references/languages/java/rules/review-code-changes.mdmarkdown541 B
references/languages/java/rules/troubleshooting.mdmarkdown2.5 KB
references/languages/java/rules/upgrade-strategy.mdmarkdown1.4 KB
references/languages/java/rules/upgrade-success-criteria.mdmarkdown686 B
references/languages/java/scripts/upgrade_bom.pyscript19.6 KB
references/languages/java/templates/PLAN_TEMPLATE.mdmarkdown9.4 KB
references/languages/java/templates/PROGRESS_TEMPLATE.mdmarkdown9.1 KB
references/languages/java/templates/SUMMARY_TEMPLATE.mdmarkdown8.6 KB
references/languages/java/workflow/phase-1-precheck.mdmarkdown2.3 KB
references/languages/java/workflow/phase-2-plan.mdmarkdown2.9 KB
references/languages/java/workflow/phase-3-execute.mdmarkdown2.4 KB
references/languages/java/workflow/phase-4-summarize.mdmarkdown1.1 KB
references/services/functions/assessment.mdmarkdown4.2 KB
references/services/functions/automation.mdmarkdown13.6 KB
references/services/functions/consumption-to-flex.mdmarkdown10.9 KB
references/services/redis/redis-to-amr.mdmarkdown7.5 KB
references/workflow-details.mdmarkdown1.9 KB

references/languages/java/workflow/phase-2-plan.md

View on GitHub
# Phase 2: Generate Upgrade Plan

Load this file when executing Phase 2. Refer back to [`upgrade-success-criteria`](../rules/upgrade-success-criteria.md) and [`upgrade-strategy`](../rules/upgrade-strategy.md) for success criteria and strategy, and [`../rules/troubleshooting.md`](../rules/troubleshooting.md) when failures occur.

## 1. Initialize

1. Update `plan.md`: replace all remaining placeholders
2. Extract user-specified guidelines from prompt into "Guidelines" section (bulleted list; leave empty if none)

## 2. Environment Analysis

1. Read HTML comments in "Available Tools" section of `plan.md` to understand rules and expected format
2. Record discovered JDK versions and paths
3. Detect wrapper presence; if wrapper exists, read wrapper properties to determine build tool version
4. Check build tool version compatibility with JDK — flag incompatible versions for upgrade

## 3. Dependency Analysis

1. Read HTML comments in "Technology Stack" and "Derived Upgrades" sections of `plan.md` to understand rules and expected format
2. Identify core tech stack across **ALL modules** (direct deps + upgrade-critical deps)
3. Include build tool (Maven/Gradle) and build plugins (`maven-compiler-plugin`, `maven-surefire-plugin`, etc.) in the technology stack analysis
4. Flag EOL dependencies (high priority for upgrade)
5. Consult the Migration Guidelines for package mappings and migration guides
6. Populate "Technology Stack" and "Derived Upgrades"

## 4. Upgrade Path Design

1. Read HTML comments in "Key Challenges" and "Upgrade Steps" sections of `plan.md` to understand rules and expected format
2. For incompatible deps, prefer: Replacement > Adaptation > Rewrite
3. Finalize "Available Tools" section based on the planned step sequence
4. Design step sequence:
   - **Step 1 (MANDATORY)**: Setup Baseline — run compile/test with current JDK, document results
   - **Steps 2-N**: Upgrade steps — dependency order, high-risk early, isolated breaking changes. Compilation must pass (both main and test code); test failures documented for Final Validation.
   - **Final step (MANDATORY)**: Final Validation — verify all goals met, all TODOs resolved, achieve **Upgrade Success Criteria** through iterative test & fix loop.
5. Identify high-risk areas for "Key Challenges" section
6. Write steps following format in `plan.md`

## 5. Plan Review

1. Verify all placeholders filled in `plan.md`, check for missing coverage/infeasibility/limitations
2. Revise plan as needed for completeness and feasibility; document unfixable limitations in "Plan Review" section
3. Ensure all sections of `plan.md` are fully populated (per **Template compliance** rule) and all HTML comments removed

After plan generation, proceed directly to execution — create `.github/java-upgrade/{RUN_ID}/progress.md` from the Progress Template, replace placeholders, and begin execution. Log the migration plan, then proceed without pausing for confirmation.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall