docs: add Community Schemas section + README entry#1043
Merged
TabishB merged 1 commit intoFission-AI:mainfrom May 4, 2026
Merged
docs: add Community Schemas section + README entry#1043TabishB merged 1 commit intoFission-AI:mainfrom
TabishB merged 1 commit intoFission-AI:mainfrom
Conversation
Adds a "Community Schemas" section to docs/customization.md cataloging community-maintained schema bundles distributed via standalone repositories. Modeled after github/spec-kit's community extension catalog (https://github.com/github/spec-kit/tree/main/extensions). The first entry is `superpowers-bridge` from JiangWay/openspec-schemas — born from the proposal in PR Fission-AI#970 and now maintained externally. Also adds a brief 4-line "Community schemas" introductory section in README.md (between Docs and Why OpenSpec) pointing readers to the catalog. Documentation only; no code or schema changes. Refs: Fission-AI#970 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe PR adds documentation for community-maintained OpenSpec schemas. README.md introduces the concept with a link to detailed docs, while docs/customization.md provides installation instructions and a community schema registry table. ChangesCommunity Schemas Documentation
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Review rate limit: 7/8 reviews remaining, refill in 7 minutes and 30 seconds.Comment |
JiangWay
pushed a commit
to JiangWay/openspec-schemas
that referenced
this pull request
May 2, 2026
Evidence-first 6-section retrospective covering the brainstorm → plan → execute → response cycle that produced this repo. Wins: external-repo strategy worked, ate own dog food end-to-end, fact-check culture held under pressure, bilingual from start, atomic commits. Misses: 2b dead-code only caught by user, README/INTEGRATION 60% overlap not caught until audit, OAuth workflow scope blocked first push, T8 orphan heading, final code-reviewer hit Stream idle timeout. Plan deviations: pivoted from 'modify PR #970 in-place' to external repo + small docs PR; dropped 2b after fact-check; consolidated INTEGRATION into bridge README. Surprises: spec-kit ecosystem already had 2 superpowers bridges; executing-plans SKILL.md is dramatically thinner than subagent-driven-development; OAuth workflow scope is a real thing. Promote candidates: doc-overlap audit checklist, schema dead-code detection, fact-check-before-defending culture (already noted). Refs: - PR #970: Fission-AI/OpenSpec#970 - PR #1043: Fission-AI/OpenSpec#1043 - Issue #780: Fission-AI/OpenSpec#780
TabishB
approved these changes
May 4, 2026
Contributor
There was a problem hiding this comment.
Nice, I'm ok with supporting this! It's easy and lightweight. We want to try and find better ways to support community plugins/extensions. Just not a priority at the moment.
Edit: p.s we're looking to hire some full-time contributors for OpenSpec. If you're interested feel free to reach out here: tabish@openspec.dev
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
2 participants
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 a "Community Schemas" section to
docs/customization.mdlisting community-maintained OpenSpec schemas distributed via standalone repositories. Modeled after github/spec-kit's community extension catalog.Also adds a brief 4-line "Community schemas" introductory section in
README.mdpointing to the new catalog.The first catalog entry is
superpowers-bridge— born from the proposal in #970 and now living at JiangWay/openspec-schemas.This PR adds documentation only; no code or schema changes. Each row in the catalog represents a separately-maintained external repository.
Test plan
Maintainer note
Easy to partially accept — the README addition is a separate hunk from the
docs/customization.mdaddition. If you'd prefer keeping the README focused (without a community-schemas entry), happy to revise to just the docs change.Refs: #970
🤖 Generated with Claude Code
Summary by CodeRabbit