Add SpecTest extension to community catalog#2159
Merged
mnriem merged 4 commits intogithub:mainfrom Apr 10, 2026
Merged
Conversation
Adds spec-kit-spectest: auto-generate test scaffolds from spec criteria. 4 commands: - /speckit.test.generate — generate framework-native test scaffolds - /speckit.test.coverage — map spec requirements to test coverage - /speckit.test.gaps — find untested requirements with suggestions - /speckit.test.plan — generate structured test plan documents 1 hook: after_implement (gap detection) Bridges the spec-to-test gap in the SDD workflow.
Contributor
There was a problem hiding this comment.
Pull request overview
Adds the community catalog/README entries for the new SpecTest extension so it can be discovered and installed via Spec Kit’s community extensions catalog.
Changes:
- Add SpecTest row to the community extensions table in
README.md. - Add spectest entry to
extensions/catalog.community.jsonand bump the catalogupdated_at.
Show a summary per file
| File | Description |
|---|---|
| README.md | Adds SpecTest to the Community Extensions table. |
| extensions/catalog.community.json | Adds the SpecTest catalog entry and updates top-level updated_at. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 1
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
…ot review Set both to 2026-04-10T16:00:00Z instead of midnight.
mnriem
approved these changes
Apr 10, 2026
…in-bilal/spec-kit into feat/spectest-extension
Contributor
There was a problem hiding this comment.
Pull request overview
Adds the SpecTest community extension to Spec Kit’s community extension catalog, making it discoverable/installable via the standard catalog flow.
Changes:
- Added a new
spectestentry toextensions/catalog.community.json(including metadata, version, URLs, tags, and timestamps). - Added the SpecTest row to the Community Extensions table in the root
README.md.
Show a summary per file
| File | Description |
|---|---|
| README.md | Adds SpecTest to the Community Extensions table so users can find the extension. |
| extensions/catalog.community.json | Registers the spectest extension in the community catalog and bumps top-level updated_at. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 0 new
Collaborator
|
Thank you! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds SpecTest — auto-generate test scaffolds from spec acceptance criteria, map requirement-level
coverage, find untested requirements, and produce structured test plans.
Extension repo: https://github.com/Quratulain-bilal/spec-kit-spectest
The Problem
Spec Kit produces detailed acceptance criteria, user scenarios, and success criteria — but testing is
completely manual. Developers write tests from memory instead of tracing back to spec requirements.
There's no way to measure "spec coverage" or find requirements that slipped through without any tests.
What SpecTest Does
4 commands that connect specs to tests:
/speckit.test.generate/speckit.test.coverage/speckit.test.gaps/speckit.test.plan1 hook:
after_implement(scan for untested requirements)Why This Matters
Bridges the spec-to-test gap in the SDD workflow:
specify → plan → tasks → implement → SpecTest → tests ✅
Checklist
extension.ymlfollows schema v1.0speckit-utilsandstaff-review)Spec SyncandStaff Review Extension)updated_atbumped monotonically (2026-04-10T16:00:00Z > previous 2026-04-10T12:34:56Z)extension.ymlreferences