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-3-execute.md

View on GitHub
# Phase 3: Execute Upgrade Plan

Load this file when executing Phase 3. 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. Read `plan.md` for step details
2. Update `progress.md`:
   - Replace `<RUN_ID>`, `<PROJECT_NAME>` and timestamp placeholders
   - Create step entries for each step in `plan.md` (per **Template compliance** rule)

## 2. Execute

For each step:

1. Read `plan.md` for step details and guidelines
2. Mark ⏳ in `progress.md`
3. Make changes as planned (use OpenRewrite if helpful, verify results)
   - Add TODOs for any deferred work, e.g., temporary workarounds
4. **Review Code Changes** (per rules in Progress Template): Verify sufficiency (all required changes present) and necessity (no unnecessary changes, functional behavior preserved, security controls maintained).
   - Add missing changes and revert unnecessary changes. Document any unavoidable behavior changes with justification.
5. Verify with specified command/JDK:
   - **Steps 1-N (Setup/Upgrade)**: Compilation must pass (including both main and test code, fix immediately if not). Test failures acceptable — document count.
   - **Final Validation Step**: Achieve **Upgrade Success Criteria** — iterative test & fix loop until 100% pass (or ≥ baseline). NO deferring. See [`../rules/troubleshooting.md`](../rules/troubleshooting.md) when stuck.
   - Build: `mvn clean test-compile` (or `./gradlew compileTestJava` for Gradle)
   - Test: `mvn clean test` (or `./gradlew test` for Gradle)
6. Commit on the `java-upgrade/{RUN_ID}` branch with message format (if git available; otherwise, log details in `progress.md`):
   - First line: `Step <x>: <title> - Compile: <result>` or `Step <x>: <title> - Compile: <result>, Tests: <pass>/<total> passed` (if tests run)
   - Body: Changes summary + concise known issues/limitations (≤5 lines)
   - **Security note**: If any security-related changes were made, include "Security: <change description and justification>"
7. Update `progress.md` with step details and mark ✅ or ❗

## 3. Complete

1. Validate all steps in `plan.md` have ✅ in `progress.md`
2. Validate all **Upgrade Success Criteria** are met, or otherwise go back to Final Validation step to fix
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