Run azure-cosmos integration/customer-workflow tests locally, closely following the CI pipeline (build+install, then failsafe verify with a test profile) using one consistent JDK for both steps. USE WHEN: asked to run cosmos integration tests, customer-workflow tests (fi-customer-workflows / fi-sm-customer-workflows)…
Analyzes GPT-RAG boundaries, contracts, security, deployment topology, and trade-offs. Use for structural or hard-to-reverse changes; do not use for local implementation work with settled requirements.
Prepares and validates GPT-RAG multi-repository releases. Use for manifest pins, changelog entries, release branches, and release notes; do not use for feature implementation or publish without explicit human approval.
Conducts and records a verifiable GPT-RAG architectural decision. Use when a choice alters repositories, boundaries, contracts, identity, data, deployment topology, or operation with meaningful reversal cost.
Keeps GPT-RAG user and operator documentation aligned with shipped behavior. Use for features, configuration keys, deployment parameters, defaults, component pins, operations, or breaking changes.
GPT-RAG architecture and implementation principles. Use for design, review, meaningful refactoring, Azure integration, security, testing, or operational changes.
Prepares and validates GPT-RAG umbrella and multi-repository releases. Use whenever work involves release preparation, semantic versions, release branches, manifest or component pins, changelog release entries, tags, GitHub Release notes, or AI Landing Zone release alignment.
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
Enforce consistent struct design conventions across sdk/cosmos crates. Validates visibility modifiers, field privacy, #[nonexhaustive] usage, and construction API patterns (Default/new with with setters, or optional separate builders with builder()/build()), and construction correctness on public structs. Can auto-fix…
Submit or retire an azd template in the awesome-azd gallery. Use when asked to submit, add, contribute, remove, retire, or clean up a template in awesome-azd. New submissions require only a GitHub repository URL — all metadata (title, description, languages, frameworks, Azure services, IaC) is auto-detected by the…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: