Azure cloud development import infrastructure

[anderseide]

Pull Request Checklist

• I have read and followed the CONTRIBUTING.md guidelines.
• My contribution adds a new instruction, prompt, agent, skill, or workflow file in the correct directory.
• The file follows the required naming convention.
• The content is clearly structured and follows the example format.
• I have tested my instructions, prompt, agent, skill, or workflow with GitHub Copilot.
• I have run npm start and verified that README.md is up to date.

---

Description

• Added skill that exports existing infrastructure to terraform code using the Azure Verified Modules
• Updated plugin to include the skill
• Added additional tools to the Azure Terraform IaC Implementation Specialist agent to make it more efficient

---

Type of Contribution

• New instruction file.
• New prompt file.
• New agent file.
• New plugin.
• New skill file.
• New agentic workflow.
• Update to existing instruction, prompt, agent, plugin, skill, or workflow.
• Other (please specify):

---

Additional Notes

---

By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

[Copilot]

Pull request overview

This PR introduces a new Azure-focused skill for exporting existing (live) Azure infrastructure into AVM-based Terraform, and wires it into the Azure cloud development plugin and repo documentation. It also updates the Terraform Azure implementation agent’s tool configuration.

Changes:

• Added a new skill: import-infrastructure-as-code (Azure discovery → AVM selection → Terraform generation/import/validation workflow).
• Updated azure-cloud-development plugin manifest/version to include the new skill.
• Updated docs indexes for skills/plugins and modified the Terraform Azure implement agent tool list.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
skills/import-infrastructure-as-code/SKILL.md	New skill defining a detailed workflow for discovering Azure resources and generating AVM-based Terraform/import addresses.
plugins/azure-cloud-development/.github/plugin/plugin.json	Bumps plugin version and adds the new skill to the plugin manifest.
docs/README.skills.md	Adds the new skill to the skills index.
docs/README.plugins.md	Updates the azure-cloud-development plugin “Items” count to reflect the added skill.
agents/terraform-azure-implement.agent.md	Updates the agent’s allowed tools list.

Comments suppressed due to low confidence (1)

agents/terraform-azure-implement.agent.md:21

• The front-matter tools list was changed to execute/*, read/*, web/fetch, todo, etc., but the agent instructions below still reference tools that are no longer in the allowed list (#runCommands, #fetch, #todos, #azureterraformbestpractices, #microsoft-docs, #get_bestpractices). This mismatch will prevent the agent from following its own workflow. Either update the tools: list to include the referenced tools, or update the instructions to use the new tool names consistently (and remove references to tools that aren’t available).

tools: [execute/getTerminalOutput, execute/awaitTerminal, execute/runInTerminal, read/problems, read/readFile, read/terminalSelection, read/terminalLastCommand, agent, edit/createDirectory, edit/createFile, edit/editFiles, search, web/fetch, 'azure-mcp/*', todo]
---

# Azure Terraform Infrastructure as Code Implementation Specialist

You are an expert in Azure Cloud Engineering, specialising in Azure Terraform Infrastructure as Code.

## Key tasks

- Review existing `.tf` files using `#search` and offer to improve or refactor them.
- Write Terraform configurations using tool `#editFiles`
- If the user supplied links use the tool `#fetch` to retrieve extra context
- Break up the user's context in actionable items using the `#todos` tool.
- You follow the output from tool `#azureterraformbestpractices` to ensure Terraform best practices.
- Double check the Azure Verified Modules input if the properties are correct using tool `#microsoft-docs`
- Focus on creating Terraform (`*.tf`) files. Do not include any other file types or formats.
- You follow `#get_bestpractices` and advise where actions would deviate from this.
- Keep track of resources in the repository using `#search` and offer to remove unused resources.

[aaronpowell]

it looks like you've branched off the main branch, not staged meaning you have all the materialised plugin files.

You can fix this with:

git fetch origin staged
git rebase --onto origin/staged origin/main <your branch name>
git push --force-with-lease

Or by using the script npm run plugin:clean

[anderseide]

Thanks @aaronpowell . Ran the git commands you listed. Sorry for not catching that important detail in the contributing guidelines. A lot of changes though, so not sure if I missed something else

[aaronpowell]

Probably best to run npm run plugin:clean then, that'll fix the plugins cache

[anderseide]

@aaronpowell there we go. All checks have passed and a more decent number of changes