zava-agent-config

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.