docs(community): add openspec-guard

[guillaume-flambard]

Motivation

docs/community.md invites projects built with or for OpenSpec to add themselves
through a pull request. openspec-guard reads openspec/specs and reports which
scenarios have a test in front of them, which is squarely "supporting its use".

What it does

• Adds one entry under "Projects and resources", in the existing format.

Proof it works

• The entry follows the file's rules: a direct link, a description of what people
  can use, no promotional claim, no referral or tracking link. MIT, no paid
  features and no account required, so there is nothing to disclose on that front.
• Rendered docs/community.md through GitHub's Markdown API and checked the link
  resolves and the list renders as one item per project.
• git diff --check passed.
• No changeset: this changes documentation only and does not affect users of the
  package.

Closes #1844.

Disclosure

Written with Claude Opus 5 in Claude Code, reviewed and verified by me before
opening. CONTRIBUTING asks contributors to say so.

Summary by CodeRabbit

• Documentation
  • Added openspec-guard to the community showcase’s projects and resources list.
  • Documented its ability to report which OpenSpec scenarios are covered by Vitest or Jest tests without executing those tests.
  • Included a link to the project repository for additional details and access.
  • Expanded the community resource directory with another tool for reviewing test coverage.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: Fission-AI/OpenSpec/.coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 706fcbab-4446-4e23-9981-1efd5ece61f9

📥 Commits

Reviewing files that changed from the base of the PR and between c19c80a and 109cf06.

📒 Files selected for processing (1)

• docs/community.md

🚧 Files skipped from review as they are similar to previous changes (1)

• docs/community.md

Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review.

---

📝 Walkthrough

Walkthrough

The community showcase now lists openspec-guard, a CLI and GitHub Action that reports OpenSpec scenario coverage from Vitest or Jest tests without running them.

Changes

Community showcase

Layer / File(s)	Summary
Add openspec-guard entry docs/community.md	Adds a linked openspec-guard entry to the “Projects and resources” list.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Other

Suggested reviewers: tabishb

Merge Risk: ⚪ Minimal · up to 109cf

The documentation update is mergeable with no identified production or repository risk.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	Issue #1844 requires a direct link to https://github.com/guillaume-flambard/openspec-guard. docs/community.md links to https://github.com/guillaume-flambard/spec-guard instead. The entry covers …	Change the link to https://github.com/guillaume-flambard/openspec-guard. Update the one-line description to include the required openspec/specs input, statically extracted Vitest or Jest titles, and no-LLM behavior.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the documentation change: adding the openspec-guard project to the community section.
Out of Scope Changes check	✅ Passed	The whole-pull-request change adds one entry to docs/community.md under Projects and resources. The change directly implements issue #1844. No unrelated change is shown.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…

Full details: Linked Issues check

Explanation

Issue #1844 requires a direct link to https://github.com/guillaume-flambard/openspec-guard. docs/community.md links to https://github.com/guillaume-flambard/spec-guard instead. The entry covers the CLI, GitHub Action, Vitest or Jest coverage, and no test execution. It does not state that the tool reads openspec/specs, uses statically extracted test titles, or never calls an LLM.

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[clay-good]

LGTM. Verified against the current upstream repository: GitHub now identifies the renamed repository as guillaume-flambard/spec-guard, while package.json still names the package openspec-guard. The repository is public and MIT-licensed, and its README confirms that it reads OpenSpec scenarios, supports Vitest and Jest, and does not run tests. The canonical-link update is correct; the old URL in issue #1844 is stale after the rename. The showcase only requires disclosure when paid features or an account are required, so no absence statement is needed in the entry. git diff --check passes, and the PR remains a one-line docs-only change.

[alfred-openspec]

Reviewed the current head. The one-line community entry accurately describes the linked public MIT project, the canonical URL resolves, and all checks pass.