azure-bicep-github-copilot

🥈Silver

The azure-bicep-github-copilot repository provides essential agent modes, prompt files, and skills specifically designed for Azure Bicep, enhancing development workflows. Perfect for developers looking to streamline their infrastructure as code practices using GitHub Copilot.

910Updated 1mo ago

Intermediate15 minutes to implementdevelopment

Saves ~240 min per use

Quick InstallView Source

claude install johnlokerse/azure-bicep-github-copilot

Works with:

GitHub Copilot

Overview

About This Skill

Use Cases

Automating Azure resource deployment

Generating Bicep templates

Integrating Bicep with CI/CD pipelines

Enhancing code quality with AI suggestions

Setup & Installation

Quick Install

Terminal

claude install johnlokerse/azure-bicep-github-copilot

Alternative Install (Git Clone)

git clone https://github.com/johnlokerse/azure-bicep-github-copilot

Requirements

Claude Code or compatible AI agent
Works with: GitHub Copilot

Quick Start Guide

Install the Skill

Copy the install command above and run it in your terminal.

Open Your AI Agent

Launch Claude Code, Cursor, or your preferred AI coding agent.

Try It Out

Use the prompt template or examples below to test the skill.

Customize

Adapt the skill to your specific use case and workflow.

Usage Examples

Prompt Template

Act as an Azure Bicep expert and GitHub Copilot assistant. I'm working on a [PROJECT_TYPE] for [COMPANY] in the [INDUSTRY] sector. I need help with [SPECIFIC_BICEP_TASK]. Provide me with optimized Bicep code snippets, best practices, and potential pitfalls to avoid. Use the following context: [CONTEXT_OR_DATA].

Example Output

# Azure Bicep Resource Deployment for Web App

## Recommended Bicep Code
```bicep
resource webApp 'Microsoft.Web/sites@2022-03-01' = {
  name: 'contoso-webapp-${uniqueString(resourceGroup().id)}'
  location: resourceGroup().location
  properties: {
    serverFarmId: webAppServicePlan.id
    siteConfig: {
      appSettings: [
        {
          name: 'APPINSIGHTS_INSTRUMENTATIONKEY'
          value: reference(resourceId('microsoft.insights/components', appInsights.name)).properties.instrumentationKey
        }
      ]
    }
  }
}
```

## Best Practices
- Always use unique names for resources to avoid conflicts
- Implement proper tagging for cost tracking and management
- Consider using modules for reusable components

## Potential Pitfalls
- Ensure proper RBAC permissions are in place before deployment
- Validate your Bicep files using the Azure CLI or VS Code extension
- Be aware of regional limitations for certain resource types