Officialv1.0.03 scenarios
Bicep
Azure Bicep guidance for deployment modes, secret exposure, and subscription-target drift.
deploywhisper skill install bicep
How to use this skill
1. Install it locally
Use the install command above from any DeployWhisper app checkout that has the installer enabled.
2. Run analysis on matching artifacts
This skill activates when files or content patterns below are detected during analysis.
3. Verify behavior
Published registry data currently includes 3 deterministic scenarios for this skill.
Metadata
Author
DeployWhisper
Version
1.0.0
License
MIT
Scenarios
3
Tags
Triggers
- main.bicep
- infra.bicep
- .bicep
Content patterns
- No content pattern hints declared.
Guidance excerpt
Critical risk patterns
- Resource or module renames can change deployment identity and trigger destructive replacement = HIGH
- `existing` resources pointed at the wrong subscription or resource group create broken references = HIGH
- Key Vault secrets or sensitive outputs emitted as plain strings leak credentials = CRITICAL
- Complete-mode deployments delete unmanaged resources in the target scope = CRITICAL
Review cues
- Review Bicep deployment mode, target scope, and secret handling together before approving.
- Prefer deterministic roll-forward or rollback steps over hand-wavy remediation notes.