Skip to content

Add Catalog CI extension to community catalog#2239

Merged
mnriem merged 1 commit intogithub:mainfrom
Quratulain-bilal:add-catalog-ci-extension
Apr 16, 2026
Merged

Add Catalog CI extension to community catalog#2239
mnriem merged 1 commit intogithub:mainfrom
Quratulain-bilal:add-catalog-ci-extension

Conversation

@Quratulain-bilal
Copy link
Copy Markdown
Contributor

Summary

  • Adds catalog-ci extension to catalog.community.json (between canon and ci-guard)
  • Adds row to community extensions table in README.md
  • Bumps top-level updated_at

Extension

Checklist

  • Entry in alphabetical order
  • All required fields present
  • download_url points to tagged release
  • README table row added
  • updated_at bumped

- Adds catalog-ci entry to catalog.community.json (between canon and ci-guard)
- Adds Catalog CI row to community extensions table in README.md
- Bumps top-level updated_at
@Quratulain-bilal
Copy link
Copy Markdown
Contributor Author

Why this extension matters

The community catalog has grown to 60+ extensions — every new submission requires maintainers to manually
verify JSON structure, field formats, URL accessibility, semver compliance, and alphabetical ordering.
The EXTENSION-PUBLISHING-GUIDE.md mentions "Automated Checks (if available)" — but no such tooling
existed until now.

Catalog CI fills that gap with 4 read-only commands:

  • validate — JSON structure, required fields, ID format (^[a-z0-9-]+$), semver, alphabetical ordering,
    duplicate detection, date consistency
  • check-urls — HTTP HEAD verification of every download_url, repository, homepage, documentation, and
    changelog link
  • diff — Git-aware comparison showing exactly which entries were added/modified/removed in a PR
  • lint — Cross-checks a local extension.yml against its catalog entry to catch mismatches before
    submission

Impact for maintainers:

  • Review time drops from manual field-by-field inspection to running /speckit.catalog-ci.validate once
  • Dead links get caught before merge, not after users report broken downloads
  • PR authors can self-validate before submitting, reducing back-and-forth review cycles
  • Zero hooks, zero file writes — purely read-only, zero risk to existing workflows

This is the kind of infrastructure tooling that scales the catalog review process as the community grows
from 60 to 600 extensions.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a new community extension entry (catalog-ci) to Spec Kit’s community extension catalog and surfaces it in the root Community Extensions table so users can discover and install it.

Changes:

  • Added the catalog-ci extension metadata to extensions/catalog.community.json in alphabetical order.
  • Bumped the catalog’s top-level updated_at.
  • Added a corresponding row to the Community Extensions table in README.md.
Show a summary per file
File Description
extensions/catalog.community.json Adds catalog-ci extension entry and updates catalog timestamp.
README.md Adds Catalog CI to the community extensions table for discoverability.

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

@mnriem mnriem merged commit e0fd355 into github:main Apr 16, 2026
15 checks passed
@mnriem
Copy link
Copy Markdown
Collaborator

mnriem commented Apr 16, 2026

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants