This is an update to an existing catalog entry (cosmosdb), bumping it from v0.1.0 → v0.2.0. Only the version, download URL, and updated_at change; all other fields are unchanged.
Extension metadata
Required tools
None. The extension is prompt-template based; the generated apps target an Azure Cosmos DB (NoSQL) account or the emulator, but the extension itself has no external CLI dependencies.
Key features
- 53 prescriptive commands for Azure Cosmos DB (micro patterns, component patterns, full application scaffolds, and meta tools: recommend, advise, review, explain).
before_implement → advise and after_implement → review hooks.
- New in v0.2.0:
advise inlines its best-practice rule digest so guidance reaches /speckit.implement without a second command invocation; both hooks are non-optional; review applies fixes rather than only auditing.
What changed since the cataloged v0.1.0
speckit.cosmosdb.advise now inlines a compact best-practice rule digest for the selected patterns.
before_implement / after_implement hooks are non-optional.
speckit.cosmosdb.review applies fixes, not just an audit.
See the CHANGELOG.
Testing checklist
Submission requirements
Testing details
Installed from the v0.2.0 release archive into a Spec Kit project (--integration copilot) and exercised the specify → plan → tasks → implement flow. Verified the release archive's extension.yml reports version: 0.2.0, the manifest lists 53 commands and 2 hooks, and the advise/review hooks fire and shape the generated Azure Cosmos DB code.
Example usage
# Install the extension (from a Spec Kit project)
specify extension add cosmosdb --from https://github.com/AzureCosmosDB/spec-kit-cosmosdb/archive/refs/tags/v0.2.0.zip
# Run the normal flow; the Cosmos DB guidance shapes /speckit.plan and /speckit.implement
/speckit.specify "an appointment booking API on Azure Cosmos DB"
/speckit.plan
/speckit.tasks
/speckit.implement
Proposed catalog entry
{
"cosmosdb": {
"name": "Azure Cosmos DB",
"id": "cosmosdb",
"description": "Best-practice Azure Cosmos DB code generation and review for any AI coding agent",
"author": "Theo van Kraay (maintained on behalf of the Azure Cosmos DB team; hosted in the AzureCosmosDB org)",
"version": "0.2.0",
"download_url": "https://github.com/AzureCosmosDB/spec-kit-cosmosdb/archive/refs/tags/v0.2.0.zip",
"repository": "https://github.com/AzureCosmosDB/spec-kit-cosmosdb",
"homepage": "https://github.com/AzureCosmosDB/spec-kit-cosmosdb",
"documentation": "https://github.com/AzureCosmosDB/spec-kit-cosmosdb/blob/main/README.md",
"changelog": "https://github.com/AzureCosmosDB/spec-kit-cosmosdb/blob/main/CHANGELOG.md",
"license": "MIT",
"category": "code",
"effect": "read-write",
"requires": {
"speckit_version": ">=0.1.0"
},
"provides": {
"commands": 53,
"hooks": 2
},
"tags": [
"azure",
"cosmosdb",
"database",
"nosql",
"recommend-coding"
],
"verified": false,
"downloads": 0,
"stars": 0,
"created_at": "2026-08-21T00:00:00Z",
"updated_at": "2026-09-14T00:00:00Z"
}
}
Additional context
Update only — the existing cosmosdb entry is already in extensions/catalog.community.json at v0.1.0. This bumps version and download_url to the v0.2.0 release and refreshes updated_at; created_at and all other fields are preserved.
Extension metadata
cosmosdb>=0.1.0Required tools
None. The extension is prompt-template based; the generated apps target an Azure Cosmos DB (NoSQL) account or the emulator, but the extension itself has no external CLI dependencies.
Key features
before_implement→adviseandafter_implement→reviewhooks.adviseinlines its best-practice rule digest so guidance reaches/speckit.implementwithout a second command invocation; both hooks are non-optional;reviewapplies fixes rather than only auditing.What changed since the cataloged v0.1.0
speckit.cosmosdb.advisenow inlines a compact best-practice rule digest for the selected patterns.before_implement/after_implementhooks are non-optional.speckit.cosmosdb.reviewapplies fixes, not just an audit.See the CHANGELOG.
Testing checklist
Submission requirements
extension.ymlmanifest includedv0.2.0)Testing details
Installed from the v0.2.0 release archive into a Spec Kit project (
--integration copilot) and exercised the specify → plan → tasks → implement flow. Verified the release archive'sextension.ymlreportsversion: 0.2.0, the manifest lists 53 commands and 2 hooks, and theadvise/reviewhooks fire and shape the generated Azure Cosmos DB code.Example usage
Proposed catalog entry
{ "cosmosdb": { "name": "Azure Cosmos DB", "id": "cosmosdb", "description": "Best-practice Azure Cosmos DB code generation and review for any AI coding agent", "author": "Theo van Kraay (maintained on behalf of the Azure Cosmos DB team; hosted in the AzureCosmosDB org)", "version": "0.2.0", "download_url": "https://github.com/AzureCosmosDB/spec-kit-cosmosdb/archive/refs/tags/v0.2.0.zip", "repository": "https://github.com/AzureCosmosDB/spec-kit-cosmosdb", "homepage": "https://github.com/AzureCosmosDB/spec-kit-cosmosdb", "documentation": "https://github.com/AzureCosmosDB/spec-kit-cosmosdb/blob/main/README.md", "changelog": "https://github.com/AzureCosmosDB/spec-kit-cosmosdb/blob/main/CHANGELOG.md", "license": "MIT", "category": "code", "effect": "read-write", "requires": { "speckit_version": ">=0.1.0" }, "provides": { "commands": 53, "hooks": 2 }, "tags": [ "azure", "cosmosdb", "database", "nosql", "recommend-coding" ], "verified": false, "downloads": 0, "stars": 0, "created_at": "2026-08-21T00:00:00Z", "updated_at": "2026-09-14T00:00:00Z" } }Additional context
Update only — the existing
cosmosdbentry is already inextensions/catalog.community.jsonat v0.1.0. This bumpsversionanddownload_urlto the v0.2.0 release and refreshesupdated_at;created_atand all other fields are preserved.