Menu
Pull request conventions for trunk-based development and AKS deployment repos.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
ACR integration for AKS Automatic. Teaches attaching an ACR, image reference conventions (digest pinning, no :latest), and pull-secret-free authentication via the managed identity.
Writing idiomatic, safe, and reviewable Bicep templates for Azure resources.
Non-blocking cluster status peek — run at the end of Phases 3, 4, 5 to check AKS provisioning progress without hanging.
Voice, tone, and interaction patterns for Kickstart agents.
Configure Infrastructure phase playbook — launch the dedicated Kickstart cluster-setup view, which collects and creates the Azure resources (subscription, resource group, AKS Automatic cluster, ACR) and hands the results back to the chat.
Deploy phase playbook — build, push, apply with Azure CLI and kubectl.
| name | kickstart-github-pr-conventions |
| description | Pull request conventions for trunk-based development and AKS deployment repos. |
| disable-model-invocation | true |
Keep branches short-lived. Merge to the default branch (usually main) at least daily. Avoid long-running feature branches.
| Prefix | Use |
|---|---|
feat/<slug> | New features |
fix/<slug> | Bug fixes |
chore/<slug> | Tooling, deps, config |
deploy/<slug> | Deployment-only changes |
Use Conventional Commits format:
feat(scope): short description
Optional longer body. Explain why, not what.
Closes #<issue>
Types: feat, fix, chore, docs, test, refactor, perf, ci.
Match the first commit message. Keep under 72 characters. Start with a type prefix.
## What
Short summary of the change.
## Why
Context for the reviewer.
## How
Key implementation decisions.
## Testing
How you verified this works.
Closes #<issue>
For repos with preview environment support, each PR can trigger a deployment to a short-lived AKS namespace. Comment /deploy-preview on the PR to trigger. The deployment URL is posted back as a PR comment.
Recommended settings for the default branch: