DevExpGbb

Azure retail pricing and cost estimate workflow. Use when estimating Azure service costs, comparing SKUs or regions, building dev/uat/prd cost tables, pricing Azure Container Apps, PostgreSQL, Redis, Service Bus, Event Hubs, Storage, Key Vault, Log Analytics, or validating Azure monthly cost assumptions.

Azure cost optimization workflow for Terraform IaC and deployed resources. Use when analyzing Azure spend, reducing costs, finding right-sizing opportunities, comparing dev/uat/prd environments, or creating cost optimization recommendations for Container Apps, PostgreSQL, Redis, Service Bus, Event Hubs, Storage, Key Vault, and Log Analytics.

Azure Terraform best practices and deployment preflight workflow. Use when creating, editing, reviewing, validating, or planning infra/**/*.tf, azurerm resources, tfvars environments, Azure Container Apps infrastructure, managed identity, Key Vault, networking, observability, or Terraform deployment readiness.

Javadoc and Java API documentation guidance. Use when documenting public Java types, controllers, service contracts, records, exceptions, or non-obvious backend behavior in backend/**/*.java.

JUnit 5 testing best practices for this Java Spring Boot backend. Use when adding or reviewing backend tests, Mockito tests, parameterized tests, Spring Boot test slices, integration tests, or Maven test commands.

Spring Boot best practices for Java 21 backend work. Use when creating, reviewing, refactoring, or testing backend/**/*.java, Spring Boot controllers/services/configuration, REST APIs, external clients, resilience, logging, validation, or Flyway-backed persistence in this repository.

Analyze Terraform plan JSON output for AzureRM Provider Set-type attributes and distinguish false-positive order-only diffs from actual resource changes. Use when reviewing Terraform plans for Azure Application Gateway, Load Balancer, Firewall, Front Door, Network Security Group, route table, virtual network, private endpoint, or other azurerm resources with noisy nested block diffs.

Use this skill when a developer wants to stand up a NEW service, app, repository, or environment on the Zava golden path - phrases like 'provision', 'scaffold', 'spin up', 'bootstrap', 'create a new service/repo', 'I need a new microservice', or 'get me a repo with CI and Azure already wired up'. Also trigger when someone asks how to START a new component, where new services come from, or how to get a deployable repo with security, OIDC-to-Azure, and a deploy pipeline already configured - EVEN IF they never say 'golden path' or 'provision'. The skill gathers the service details conversationally, files the governed request through the platform's IssueOps front door, watches the run live, verifies the new repo and its live URL, and explains what was created and which guardrails were applied. Do NOT use for deploying changes to an existing service, changing infra of an already-provisioned repo, or creating arbitrary Azure resources outside the golden path.

Use this skill when the user asks to migrate, upgrade, or modernize a Next.js codebase from Next 14 to Next 15 — including phrasings like "bump next to 15", "upgrade next.js", "migrate to next 15", "next 15 upgrade", "we're stuck on next 14", or when preparing a major-version dependency PR involving next ^14.x. Also fires when the user mentions Next 15 indirect symptoms: async cookies/headers errors, sync params/searchParams warnings, fetch no longer cached by default, removed experimental.bundlePagesExternals or experimental.serverComponentsExternalPackages, react 19 peer warnings, GET route handlers losing default caching, NextRequest geo/ip removed, or asks for a migration plan / breaking changes audit on a Next 14 repo. This skill audits, classifies (SAFE / AUTOFIX / MANUAL), applies safe autofixes, and emits a phased migration plan grounded in the official Next.js 15 upgrade guide. It does NOT run the consumer's tests; it does NOT bump package.json; it emits a plan the team executes under review.

Use this skill when the user asks to migrate, upgrade, or modernize a Node.js codebase from Express 4 to Express 5 — including phrasings like "bump express to v5", "upgrade express", "migrate to express 5", "express deprecation warnings", "we're stuck on express 4", or when preparing a major-version dependency PR involving express ^4.x. Also fires when the user mentions removed Express APIs (app.del, res.send(status), the deprecated body-parser bundling), discontinued path-to-regexp 0.x patterns (e.g. unnamed wildcards `*` or optional segments `:id?`), or asks for a migration plan / breaking changes audit on an Express 4 repo. This skill audits, classifies (SAFE / AUTOFIX / MANUAL), applies safe autofixes, and emits a phased migration plan grounded in the official Express 5 migration guide. It does NOT run the consumer's tests; it emits a plan the team executes.

Pre-push panel review of staged changes by architect + security personas. Catches design flaws and security gaps before the PR is even opened. Trigger before `git push` on any branch with non-trivial changes.

Turn a meeting transcript or summary into well-structured GitHub Issues with acceptance criteria, labels, milestone, and assignees. Trigger when given a Teams transcript, meeting notes, or product-discussion summary that contains action items.

Turn a Sev-1/Sev-2 incident postmortem into a remediation PR with the fix, regression test, and runbook update. Trigger when given a postmortem document containing identified root cause + agreed remediation.

Flag water quality records that exceed contamination thresholds. Use when checking purity_score < 75, contamination_flag = 1, or identifying at-risk sites and records.

Standardize water purity, alert-rate, and site-risk metrics. Use when defining KPI calculations, ensuring metric consistency across reports, or setting up a new KPI pipeline.

Report null percentages and recommended imputations for water quality data. Use when profiling missing data, deciding imputation strategy, or assessing data completeness.

Convert water quality metrics into concise operations guidance. Use when writing executive summaries, translating KPIs into plain-language recommendations, or producing briefing narratives.

Validate expected columns and coercible dtypes in water quality datasets. Use when checking schema conformance, column presence, or type compatibility before analysis.

Use this skill when the user asks to migrate, upgrade, or modernize a Node.js codebase from Express 4 to Express 5 — including phrasings like "bump express to v5", "upgrade express", "migrate to express 5", "express deprecation warnings", "we're stuck on express 4", or when preparing a major-version dependency PR involving express ^4.x. Also fires when the user mentions removed Express APIs (app.del, res.send(status), the deprecated body-parser bundling), discontinued path-to-regexp 0.x patterns (e.g. unnamed wildcards `*` or optional segments `:id?`), or asks for a migration plan / breaking changes audit on an Express 4 repo. This skill audits, classifies (SAFE / AUTOFIX / MANUAL), applies safe autofixes, and emits a phased migration plan grounded in the official Express 5 migration guide. It does NOT run the consumer's tests; it emits a plan the team executes.

Use this skill to drive a pull request from review to green CI. It composes the review-panel as its per-PR review primitive, folds non-blocking findings as commits, pushes, and watches CI to green. Activate when a PR needs end-to-end review-and-fix before merge. This is the advanced driver skill from the Agentic SDLC track.

Use this skill to run a multi-persona expert advisory review on a labelled pull request against zava-storefront. The panel fans out to three specialist reviewers (correctness, security, test-coverage), each running in its own agent thread, plus a synthesizer that arbitrates and renders ONE recommendation comment. Activate when a PR is labelled `panel-review` or when a non-trivial PR needs a cross-cutting recommendation before merge.

PLACEHOLDER — do not invoke. This folder exists only so `apm install` has something to resolve during workshop setup. Your real skill belongs in a NEW folder under .apm/skills/<your-skill>/, generated by your harness from a Genesis design. See docs/tracks/.

gh-devlake roadmap, milestones, versioning, and release priorities. Use when asking about what's planned, what version something targets, or what issues exist for a milestone.

DevLake plugin registry and REST API integration patterns — ConnectionDef wiring, token resolution, scope handling, and typed API helpers. Use when adding plugins, modifying connections/scopes/tokens, or implementing DevLake API calls.

gh-devlake CLI architecture, command cascade flow, and design principles. Use when restructuring commands, adding new commands, fixing inconsistencies between entry points, or understanding how init/deploy/configure relate.

Read and reduce source material such as PowerPoint decks and CSV files before reusing it in prompts, labs, or workshop content. Use this when asked to ingest, summarize, or extract content from `.pptx` or `.csv` files.

Create workshop-ready labs, slide outlines, speaker notes, and facilitator content about token optimization, Copilot customization, MCP hygiene, model choice, usage visibility, and evals. Use this when asked to build or revise teaching material.

USE FOR: Evaluating prompts, instructions, agents, and context choices for token-efficient software engineering workflows. DO NOT USE FOR: Replacing security review, exposing secrets, or analyzing customer data without permission.

Generates comprehensive documentation for code following team standards. Use when you need to document functions, classes, APIs, or modules.

Generates comprehensive unit tests following enterprise patterns. Use whenever planning or generating unit tests.

Add OpenTelemetry distributed tra​cing to an HTTP service: instrument incoming requests, outgoing HTTP, and database queries. Spans exported via OTLP.

Deploy and configure Apache DevLake. Supports deployment to Azure or local Docker, plus post-deploy configuration of GitHub connections, Copilot metrics, DORA scopes, and projects. Trigger phrases include "deploy devlake", "set up devlake", "configure devlake", "devlake connections", "devlake scopes", "devlake azure", "devlake local", "install devlake".