Skip to content

Add Architecture Guard and Laravel adapter to community catalog#2430

Open
DyanGalih wants to merge 1 commit intogithub:mainfrom
DyanGalih:add-architecture-guard-extensions
Open

Add Architecture Guard and Laravel adapter to community catalog#2430
DyanGalih wants to merge 1 commit intogithub:mainfrom
DyanGalih:add-architecture-guard-extensions

Conversation

@DyanGalih
Copy link
Copy Markdown
Contributor

Added Architecture Guard and Architecture Guard Laravel extensions to the community catalog. These extensions provide continuous architecture governance and framework-specific rules for Laravel projects.

Copilot AI review requested due to automatic review settings May 1, 2026 15:11
@DyanGalih DyanGalih requested a review from mnriem as a code owner May 1, 2026 15:11
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 two new community extensions—Architecture Guard and a Laravel adapter—to Spec Kit’s extension discovery surfaces (community catalog + README listing).

Changes:

  • Updated extensions/catalog.community.json with two new extension entries and refreshed the top-level updated_at timestamp.
  • Updated the Community Extensions table in README.md to include the two new extensions.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
extensions/catalog.community.json Adds Architecture Guard + Laravel adapter metadata to the community extension catalog.
README.md Adds the two extensions to the Community Extensions markdown table for discoverability.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +71 to +74
"architecture-guard": {
"name": "Architecture Guard",
"id": "architecture-guard",
"description": "Continuous architecture governance for AI-assisted development. Reviews specs, plans, and code for architecture drift, producing structured refactor tasks and evolution proposals.",
Comment on lines +117 to +124
"speckit_version": ">=0.1.0",
"extensions": [
{
"id": "architecture-guard",
"version": ">=1.1.6",
"required": true
}
]
Copy link
Copy Markdown
Collaborator

@mnriem mnriem left a comment

Choose a reason for hiding this comment

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

Please address Copilot feedback. If not applicable, please explain why

@DyanGalih DyanGalih force-pushed the add-architecture-guard-extensions branch from 95ce7da to 26d7428 Compare May 1, 2026 22:24
@DyanGalih
Copy link
Copy Markdown
Contributor Author

DyanGalih commented May 1, 2026

Thanks for the review! I've addressed the feedback:

  1. Sorting: Fixed the alphabetical sorting in the catalog (architect-preview now correctly precedes architecture-guard).
  2. Extension Dependencies: Regarding the requires.extensions field: I'm intentionally introducing this to handle extension-to-extension dependencies. For framework-specific adapters like architecture-guard-laravel, it's critical to explicitly link them to the core engine they depend on. While the CLI doesn't enforce this yet, I'm proposing this shape as a proactive way to bootstrap dependency metadata in the community catalog. Since the current CLI safely ignores unknown keys in the requires block, this addition is non-breaking but provides immediate clarity for users and maintainers.

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

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +148 to +156
"requires": {
"speckit_version": ">=0.1.0",
"extensions": [
{
"id": "architecture-guard",
"version": ">=1.1.6",
"required": true
}
]
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