bicep-quality

Audit Bicep files for naming conventions and Azure best-practice compliance.

1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/piers-sinclair/Dostar --skill bicep-quality
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bicep-quality
Source: https://github.com/piers-sinclair/Dostar/tree/main/.claude/skills/bicep-quality
Command: npx skills add https://github.com/piers-sinclair/Dostar --skill bicep-quality

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the challenge of maintaining high-quality, maintainable, and secure infrastructure-as-code by automating the review of Bicep files against Azure best practices.

Core Features & Use Cases

  • Automated Auditing: Scans Bicep files for naming inconsistencies, hardcoded values, and architectural smells like overly large modules.
  • Best Practice Enforcement: Validates resource configurations against Azure-specific standards, including API versioning and security decorators.
  • Use Case: Before merging a pull request, use this skill to ensure all new infrastructure modules follow the project's naming conventions and security requirements without manual line-by-line review.

Quick Start

Run the bicep-quality skill on the infra directory to audit all infrastructure files for potential improvements and violations.

Frequently Asked Questions about bicep-quality

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit Bicep files for Azure best practices and naming conventions?

To audit Bicep files for Azure best practices, you can run an automated review on your infrastructure directory to scan for naming inconsistencies, hardcoded values, and structural issues before deployment.

What does infrastructure-as-code compliance enforcement check in Bicep templates?

Infrastructure-as-code compliance enforcement in Bicep templates checks resource configurations against Azure-specific standards, including API versioning, security decorators, and architectural smells like overly large modules.

Do I need Azure CLI and git to validate Bicep infrastructure files?

Yes, you need both git and Azure CLI tools installed to validate Bicep infrastructure files, as they are required to resolve file scopes and validate syntax against the target environment.

Can I use automated Bicep code review in DevOps pull request workflows?

Yes, you can use automated Bicep code review in DevOps pull request workflows to ensure all new infrastructure modules follow naming conventions and security requirements without manual line-by-line review.

What's the best way to enforce security decorators and API versioning in Bicep?

The best way to enforce security decorators and API versioning in Bicep is to apply automated best-practice enforcement that validates resource configurations against Azure-specific standards during your code review process.