AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

azure-upgrade

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).

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read microsoft--azure-upgrade at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 49

references/languages/java/rules/execution-guidelines.md

Execution Guidelines

  • Wrapper preference: Use Maven Wrapper (mvnw/mvnw.cmd) or Gradle Wrapper (gradlew/gradlew.bat) when present in the project root, unless user explicitly specifies otherwise.
  • Template compliance: Follow the HTML-comment instructions in the template reference files when creating and populating .github/java-upgrade/{RUN_ID}/plan.md, progress.md, summary.md. You may remove the HTML comments after populating each section.
  • Output directory: All plan/progress/summary files are created under .github/java-upgrade/{RUN_ID}/ in the project being migrated. Create this directory at the start of the run.
  • Uninterrupted run: Complete each phase fully without pausing for user input.
  • Git: If git is available, create a new branch java-upgrade/{RUN_ID} before starting the migration. Commit changes per step on this branch. If git is not available, log a warning and proceed — files remain uncommitted in the working directory. Use N/A for <current_branch> and <current_commit_id> placeholders.