Add Status Report extension to community catalog#1860
Add Status Report extension to community catalog#1860jwesleye wants to merge 2 commits intogithub:mainfrom
Conversation
There was a problem hiding this comment.
Pull request overview
Adds the “Project Status” community extension to Spec Kit’s community extension catalog so it can be discovered/installed via the standard extension search/add workflow.
Changes:
- Adds a new
statusentry toextensions/catalog.community.json(metadata + download URL). - Updates the community extensions table in
extensions/README.mdto include “Project Status”. - Bumps the community catalog
updated_attimestamp.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| extensions/catalog.community.json | Adds the new status extension entry and updates the catalog timestamp. |
| extensions/README.md | Adds “Project Status” to the Available Community Extensions table. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
mnriem
left a comment
There was a problem hiding this comment.
Please address Copilot feedback
7b6e84b to
931a2a4
Compare
Rename extension ID from "status" to "status-report" to avoid collision with existing KhawarHabibKhan/spec-kit-status extension. Addresses Copilot review feedback: - Use current timestamp for created_at - Correct alphabetical ordering in README table - Align version to v1.1.3 throughout Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
931a2a4 to
2ac3c3f
Compare
There was a problem hiding this comment.
Pull request overview
Adds the Status Report community extension to Spec Kit’s discovery catalog and lists it in the extensions README so users can find it and copy it into their own curated catalog.
Changes:
- Bumped
extensions/catalog.community.jsontop-levelupdated_atand added a newstatus-reportextension entry (v1.1.3). - Added “Status Report” to the Available Community Extensions table in
extensions/README.md.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| extensions/catalog.community.json | Updates catalog timestamp and registers the new status-report extension metadata. |
| extensions/README.md | Adds the extension to the community extensions table for discoverability. |
Comments suppressed due to low confidence (1)
extensions/catalog.community.json:578
- The publishing guide specifies using the current timestamp for
created_at/updated_at. These are set to a midnight value (2026-03-20T00:00:00Z); please use the actual current UTC timestamp (with time-of-day) for submission/update time instead of a rounded date.
"created_at": "2026-03-20T00:00:00Z",
"updated_at": "2026-03-20T00:00:00Z"
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Use precise UTC timestamp instead of midnight for updated_at fields - Disambiguate README link text to spec-kit-status-report Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "version": "1.1.4", | ||
| "download_url": "https://github.com/Open-Agent-Tools/spec-kit-status/archive/refs/tags/v1.1.4.zip", | ||
| "repository": "https://github.com/Open-Agent-Tools/spec-kit-status", |
There was a problem hiding this comment.
The catalog entry’s version and download_url point to v1.1.4, but the PR description/submission metadata says the extension version is 1.1.3. Please align the catalog entry (version + tag URL) with the actual published release to avoid broken installs or misleading catalog data.
| "status-report": { | ||
| "name": "Status Report", | ||
| "id": "status-report", | ||
| "description": "Display project status, feature progress, and recommended next actions across the spec-driven development workflow.", |
There was a problem hiding this comment.
For readability and to reduce future diff conflicts, keep extension keys in a consistent alphabetical order. Right now status-report is separated from the existing status entry further down; consider moving status-report next to status (with status before status-report) so related entries are adjacent.
mnriem
left a comment
There was a problem hiding this comment.
Please address Copilot feedback. Note entries in catalog are alphabetized by catalog id.
Extension Submission
Extension Name: Status Report
Extension ID:
status-reportVersion: 1.1.4
Author: Open-Agent-Tools
Repository: https://github.com/Open-Agent-Tools/spec-kit-status
Description
Display project status, feature progress, and recommended next actions across the spec-driven development workflow. Provides the
/speckit.status.reportcommand with:Changes from previous review
statustostatus-reportto avoid collision with existing KhawarHabibKhan/spec-kit-status extensionspeckit.status.reportto match requiredspeckit.{extension}.{command}patterncreated_atto use current submission timestampmainChecklist
extension.ymlmanifestextensions/catalog.community.jsonextensions/README.mdAvailable Extensions tableTesting
Tested locally on macOS with spec-kit v0.3.0 against a project with 10 features. Verified:
mainbranch🤖 Generated with Claude Code