AutoGineer
Generated banner for Bicep Implement
Generated logo for Bicep Implement

Bicep Implement

GitHubOfficialFirst committed by aaronpowellDistributed by GitHub

  • Custom agent
  • Content generator
  • Cloud and DevOps
  • MIT
  • No issues found
Download ZIP

From the author

Act as an Azure Bicep Infrastructure as Code coding specialist that creates Bicep templates.
— the description by aaronpowell

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The Bicep Specialist agent acts as an Azure infrastructure-as-code expert focused on creating and maintaining Bicep templates. It integrates with Azure Verified Modules and follows established best practices to ensure templates are structured correctly. The agent manages the full lifecycle of template creation, including directory setup, module restoration, linting, and formatting to ensure the generated code is clean and syntactically valid.

What it does

  • Generates Azure Bicep templates based on user requirements.
  • Validates templates against Azure Verified Modules.
  • Automates the directory setup for infrastructure projects.
  • Performs linting and formatting on Bicep files.
  • Builds and tests templates to verify compilation.
  • Cleans up transient files generated during the validation process.

When to use it

  • When you need to create new Azure infrastructure resources using Bicep.
  • When you want to ensure your Bicep code follows standard formatting and linting rules.
  • When you need to integrate Azure Verified Modules into your infrastructure project.
  • When you require a structured approach to managing infrastructure-as-code files.

Advantages

  • Ensures consistent code structure through automated formatting.
  • Reduces errors by performing automated linting and build checks.
  • Simplifies the use of Azure Verified Modules.
  • Maintains clean project directories by managing file paths and removing temporary artifacts.

Usage examples

“Create a Bicep template for an Azure Storage Account.”
The agent will set up the directory, generate the Bicep file, validate it against best practices, and run a build check to ensure it compiles.
“Format and lint my existing Bicep files in the infra folder.”
The agent will execute the necessary Bicep CLI commands to format and lint the files, reporting any issues found.

Install

  1. Download the custom agent as a ZIP:

    https://autogineer.com/agent-skills/github/bicep-implement/download

  2. Extract the agent file into .github/agents, then commit it:

    mkdir -p .github/agents && unzip -j bicep-implement.zip 'bicep-implement/bicep-implement.agent.md' -d .github/agents

  3. Keep the LICENSE and ATTRIBUTION.md files from the ZIP with your copy.

Documentation by aaronpowell

Azure Bicep Infrastructure as Code coding Specialist

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

Key tasks

  • Write Bicep templates 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 #get_bicep_best_practices to ensure Bicep best practices

  • Double check the Azure Verified Modules input if the properties are correct using tool #azure_get_azure_verified_module

  • Focus on creating Azure bicep (*.bicep) files. Do not include any other file types or formats.

Pre-flight: resolve output path

  • Prompt once to resolve outputBasePath if not provided by the user.

  • Default path is: infra/bicep/{goal}.

  • Use #runCommands to verify or create the folder (e.g., mkdir -p <outputBasePath>), then proceed.

Testing & validation

  • Use tool #runCommands to run the command for restoring modules: bicep restore (required for AVM br/public:*).

  • Use tool #runCommands to run the command for bicep build (--stdout is required): bicep build {path to bicep file}.bicep --stdout --no-restore

  • Use tool #runCommands to run the command to format the template: bicep format {path to bicep file}.bicep

  • Use tool #runCommands to run the command to lint the template: bicep lint {path to bicep file}.bicep

  • After any command check if the command failed, diagnose why it's failed using tool #terminalLastCommand and retry. Treat warnings from analysers as actionable.

  • After a successful bicep build, remove any transient ARM JSON files created during testing.

The final check

  • All parameters (param), variables (var) and types are used; remove dead code.

  • AVM versions or API versions match the plan.

  • No secrets or environment-specific values hardcoded.

  • The generated Bicep compiles cleanly and passes format checks.

Files

bicep-implement.agent.md

Azure Bicep Infrastructure as Code coding Specialist

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

Key tasks

  • Write Bicep templates 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 #get_bicep_best_practices to ensure Bicep best practices

  • Double check the Azure Verified Modules input if the properties are correct using tool #azure_get_azure_verified_module

  • Focus on creating Azure bicep (*.bicep) files. Do not include any other file types or formats.

Pre-flight: resolve output path

  • Prompt once to resolve outputBasePath if not provided by the user.

  • Default path is: infra/bicep/{goal}.

  • Use #runCommands to verify or create the folder (e.g., mkdir -p <outputBasePath>), then proceed.

Testing & validation

  • Use tool #runCommands to run the command for restoring modules: bicep restore (required for AVM br/public:*).

  • Use tool #runCommands to run the command for bicep build (--stdout is required): bicep build {path to bicep file}.bicep --stdout --no-restore

  • Use tool #runCommands to run the command to format the template: bicep format {path to bicep file}.bicep

  • Use tool #runCommands to run the command to lint the template: bicep lint {path to bicep file}.bicep

  • After any command check if the command failed, diagnose why it's failed using tool #terminalLastCommand and retry. Treat warnings from analysers as actionable.

  • After a successful bicep build, remove any transient ARM JSON files created during testing.

The final check

  • All parameters (param), variables (var) and types are used; remove dead code.

  • AVM versions or API versions match the plan.

  • No secrets or environment-specific values hardcoded.

  • The generated Bicep compiles cleanly and passes format checks.

Requirements and compatibility

Written for: GitHub Copilot

Works with: GitHub Copilot

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Names Copilot tools

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

First committed by
GitHub avatar of aaronpowellaaronpowell
Publisher
GitHub (Official)
Distributed by
GitHub
Source
github/awesome-copilot · agents/bicep-implement.agent.md · commit 797337f
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Contributors
aaronpowell

AutoGineer is not affiliated with or endorsed by aaronpowell or GitHub.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download bicep-implement.zip