Run: https://github.com/Azure/git-ape/actions/runs/35653815926
Features assessed: 8 agents, 15 skills, destroy/deploy workflow templates
Coverage: 20 / 23 covered · Gaps found: 1 drift + 3 previously-uncovered skills
Proposed this run: draft PR — docs(workshops): align destroy lifecycle content with Azure Deployment Stacks
Gaps & proposed work
| Feature |
Type |
Persona / Track |
Action |
Status |
Destroy lifecycle (git-ape-destroy.yml / stack teardown) |
workflow behavior |
DevOps-SRE / T3 (+ T2) |
Drift fix — Track 3 Lab 6 and Track 2 Lab 5 described the old az group delete / single-RG teardown; actual behavior is az stack sub delete --action-on-unmanage deleteAll against an Azure Deployment Stack, plus a soft-delete purge sweep |
In PR |
azure-stack-deploy |
skill |
DevOps-SRE / T3 |
Named in Track 3 Lab 1 as the local/VS Code equivalent of the CI deploy step; added to glossary |
In PR |
azure-stack-destroy |
skill |
DevOps-SRE / T3 (+ T2 cleanup) |
Named in Track 3 Lab 6 and Track 2 Lab 5 cleanup steps; added to glossary |
In PR |
azure-resource-availability |
skill |
Engineer / T2 |
Added to the SKU/quota failure-mode table in Track 2 Lab 2; added to glossary |
In PR |
azure-rest-api-reference |
skill |
— (internal, agent-facing) |
Used internally by azure-template-generator when authoring template properties; no distinct learner-facing action to attach it to without inventing content |
Deferred |
azure-requirements-gatherer |
agent |
— (internal, agent-facing) |
user-invocable: false; already exercised implicitly whenever labs run @git-ape deploy ... (Track 1 Lab 2, Track 2 Lab 2, Track 3 Lab 1/2) |
In sync — implicit coverage |
aws-* style out-of-scope skills |
skill |
— |
Out of scope — program is Azure-focused per workshop scope filter |
Not applicable |
Coverage detail
- Confirmed drift by reading source:
.github/skills/azure-stack-destroy/SKILL.md, .github/skills/azure-stack-deploy/SKILL.md, and the onboarding-scaffolded .github/skills/git-ape-onboarding/templates/workflows/git-ape-destroy.yml / git-ape-deploy.yml all confirm the stack-based (az stack sub create / az stack sub delete --action-on-unmanage deleteAll) primitive is what actually ships. The Track 3 deck (3_platform-engineering_deck.md) already described this correctly — only the two lab markdown files had drifted, likely predating the Deployment Stacks migration (Azure/git-ape#30).
azure-resource-availability and azure-rest-api-reference both showed 0 refs in the inventory. azure-resource-availability has a clear learner-facing hook (SKU/quota deployment failures, already a documented failure mode in Track 2 Lab 2) — added there. azure-rest-api-reference is purely an internal correctness aid for the template-generator agent (fetches ARM schema/API-version references) with no distinct learner action — adding a lab step for it would mean inventing a scenario, so it is deferred rather than force-fit.
azure-requirements-gatherer shows 0 refs but is user-invocable: false and is already invoked transparently by every @git-ape deploy ... flow across Tracks 1–3 labs. Coverage is implicit and adequate; flagging it as a hard gap would be a false positive from the grep-proxy.
- No persona ambiguity for the changes made this run — all four items map cleanly to existing Track 2 (Engineer, hands-on) and Track 3 (DevOps/SRE/platform) personas.
- Reviewed
website/docs/workshops/* mirrors: these are short overview/index pages (labs table + prerequisites), not full lab text — no drift found there, none required updating.
- One open issue (
#350) matched a workshop-sync-style search but was filtered by integrity policy and could not be read this run; could not confirm its label/content, so no Closes reference was added to the PR.
Recommended next steps
- Consider a small learner-facing scenario for
azure-rest-api-reference in a future Track 2 lab revision if a natural hook emerges — not forced this run.
- No action needed on
azure-requirements-gatherer — coverage is adequate via existing deploy-flow labs.
- A human should confirm whether issue
#350 is a workshop-sync backlog item; it was unreadable to this agent due to integrity policy filtering.
Generated by Workshop Content Auto-Updater · copilot · auto · 153 AIC · ⌖ 8.47 AIC · ⊞ 11K · ◷
Run: https://github.com/Azure/git-ape/actions/runs/35653815926
Features assessed: 8 agents, 15 skills, destroy/deploy workflow templates
Coverage: 20 / 23 covered · Gaps found: 1 drift + 3 previously-uncovered skills
Proposed this run: draft PR — docs(workshops): align destroy lifecycle content with Azure Deployment Stacks
Gaps & proposed work
git-ape-destroy.yml/ stack teardown)az group delete/ single-RG teardown; actual behavior isaz stack sub delete --action-on-unmanage deleteAllagainst an Azure Deployment Stack, plus a soft-delete purge sweepazure-stack-deployazure-stack-destroyazure-resource-availabilityazure-rest-api-referenceazure-template-generatorwhen authoring template properties; no distinct learner-facing action to attach it to without inventing contentazure-requirements-gathereruser-invocable: false; already exercised implicitly whenever labs run@git-ape deploy ...(Track 1 Lab 2, Track 2 Lab 2, Track 3 Lab 1/2)aws-*style out-of-scope skillsCoverage detail
.github/skills/azure-stack-destroy/SKILL.md,.github/skills/azure-stack-deploy/SKILL.md, and the onboarding-scaffolded.github/skills/git-ape-onboarding/templates/workflows/git-ape-destroy.yml/git-ape-deploy.ymlall confirm the stack-based (az stack sub create/az stack sub delete --action-on-unmanage deleteAll) primitive is what actually ships. The Track 3 deck (3_platform-engineering_deck.md) already described this correctly — only the two lab markdown files had drifted, likely predating the Deployment Stacks migration (Azure/git-ape#30).azure-resource-availabilityandazure-rest-api-referenceboth showed 0 refs in the inventory.azure-resource-availabilityhas a clear learner-facing hook (SKU/quota deployment failures, already a documented failure mode in Track 2 Lab 2) — added there.azure-rest-api-referenceis purely an internal correctness aid for the template-generator agent (fetches ARM schema/API-version references) with no distinct learner action — adding a lab step for it would mean inventing a scenario, so it is deferred rather than force-fit.azure-requirements-gatherershows 0 refs but isuser-invocable: falseand is already invoked transparently by every@git-ape deploy ...flow across Tracks 1–3 labs. Coverage is implicit and adequate; flagging it as a hard gap would be a false positive from the grep-proxy.website/docs/workshops/*mirrors: these are short overview/index pages (labs table + prerequisites), not full lab text — no drift found there, none required updating.#350) matched a workshop-sync-style search but was filtered by integrity policy and could not be read this run; could not confirm its label/content, so noClosesreference was added to the PR.Recommended next steps
azure-rest-api-referencein a future Track 2 lab revision if a natural hook emerges — not forced this run.azure-requirements-gatherer— coverage is adequate via existing deploy-flow labs.#350is aworkshop-syncbacklog item; it was unreadable to this agent due to integrity policy filtering.