From 74a71cbacfba1fe0825a3e806f83e3d3c697e342 Mon Sep 17 00:00:00 2001 From: Manfred Riem <15701806+mnriem@users.noreply.github.com> Date: Wed, 27 May 2026 16:11:22 -0500 Subject: [PATCH 1/2] docs: update landing page stats and branch naming convention MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Update community extensions: 91 → 105 - Update extension authors: 50+ → 60+ - Update presets: 18 → 22 - Update GitHub stars: 96K+ → 106K+ - Add last-updated date to landing page - Clarify branch naming convention for PR-only changes --- AGENTS.md | 11 ++++++----- docs/index.md | 10 ++++++---- 2 files changed, 12 insertions(+), 9 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 448ccd37e9..b6e3a28f5f 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -381,25 +381,26 @@ Implementation: Extends `YamlIntegration` (parallel to `TomlIntegration`): ## Branch Naming Convention -All branches **must** follow this pattern: +Branches follow one of two patterns depending on whether an issue exists: ``` -/- +/- # when an issue is created first +/ # when no issue exists (PR-only changes) ``` -Where `` is either an issue number or a PR number — whichever is created first. +When an issue exists, include its number immediately after the prefix — this is what makes branches traceable. For small or self-contained changes that go straight to a PR without a tracking issue, omit the number. | Prefix | When to use | Example | |---|---|---| | `feat/` | New features | `feat/2342-workflow-cli-alignment` | | `fix/` | Bug fixes | `fix/2653-paths-only-validation` | -| `docs/` | Documentation changes | `docs/2677-branch-naming-convention` | +| `docs/` | Documentation changes | `docs/2677-branch-naming-convention`, `docs/update-landing-stats` | | `community/` | Community catalog additions | `community/2492-add-mde-extension` | | `chore/` | Maintenance, tooling, CI | `chore/2366-editorconfig` | **Rules:** -1. Always include the issue or PR number immediately after the prefix — this is what makes branches traceable +1. Include the issue number when one exists — this is what makes branches traceable 2. Use kebab-case for the slug 3. Keep the slug short — enough to identify the work without looking up the issue diff --git a/docs/index.md b/docs/index.md index e44bebd246..7e46a2abea 100644 --- a/docs/index.md +++ b/docs/index.md @@ -43,7 +43,7 @@ Run `specify init` with your agent of choice and Spec Kit sets up the right comm ### Make it your own -91 community extensions (50+ authors), 18 presets, and growing. Tune the core process with presets, extend it with extensions, orchestrate it with workflows, or replace it entirely. Build and publish your own. +105 community extensions (60+ authors), 22 presets, and growing. Tune the core process with presets, extend it with extensions, orchestrate it with workflows, or replace it entirely. Build and publish your own. Including entirely different SDD processes: @@ -82,7 +82,7 @@ Community extensions like CI Guard and Architecture Guard add compliance gates a
- 96K+ + 106K+ GitHub stars
@@ -94,11 +94,11 @@ Community extensions like CI Guard and Architecture Guard add compliance gates a Integrations
- 91 + 105 Extensions
- 18 + 22 Presets
@@ -150,3 +150,5 @@ specify init my-project --integration copilot Ready to start? Follow the [Quick Start Guide](quickstart.md).
+ +

Last updated: May 27, 2026

From f2192fa83588c6b8e5d9ede22d9491429930db0f Mon Sep 17 00:00:00 2001 From: Manfred Riem <15701806+mnriem@users.noreply.github.com> Date: Wed, 27 May 2026 16:15:49 -0500 Subject: [PATCH 2/2] Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --- docs/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/index.md b/docs/index.md index 7e46a2abea..c8b02d98cb 100644 --- a/docs/index.md +++ b/docs/index.md @@ -151,4 +151,4 @@ Ready to start? Follow the [Quick Start Guide](quickstart.md).
-

Last updated: May 27, 2026

+

Last updated: May 27, 2026