feat(registry): add community section with recommended:false (S3 from retrospective)#899
Merged
Merged
Conversation
…ills (S3) Implement S3 from the 2026-05-21..25 retrospective: catalog the community tier explicitly so consumers can tell "core / curated" from "experimental / not yet eval-backed". Until now skills/midstream/community/* were loaded at runtime but invisible in skills/registry.yaml, which Codex flagged in the multi-perspective review as a scaling risk. Add a new "Community Skills (Experimental)" subsection between the core midstream block and the downstream block. Six skills listed: - rr-midstream-a11y-accessible-name-001 (pre-existing) - rr-midstream-nextjs-app-router-boundary-001 (pre-existing) - rr-midstream-modern-web-semantic-001 (#873) - rr-midstream-modern-web-performance-001 (#875) - rr-midstream-modern-web-browser-compat-001 (#881) - rr-midstream-modern-web-a11y-interactive-001 (#884) All six are marked `recommended: false` so the catalog reflects current truth: useful as opt-in suggestions, not first-line gates. The block also carries a comment explaining the convention — a community skill becomes a `recommended: true` candidate when it gains good/bad fixtures and a golden output (the S1 convention queued for a later PR). No code change; node scripts/validate-meta-consistency.mjs and npm run skills:validate both pass. npm test: 1087/1087 green. Refs: docs/development/retrospectives/2026-05-21-25.md (S3 entry). Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
River Reviewer
選択されたスキル (0)
スキップされたスキル (87)
優先度サマリー
スコア (参考値)結果(スコア): 96/100 内訳:
指摘
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Comment on lines
+276
to
+281
| name: 'Next.js App Router Boundary Guard' | ||
| path: skills/midstream/community/rr-midstream-nextjs-app-router-boundary-001/SKILL.md | ||
| category: midstream | ||
| phase: midstream | ||
| tags: [community, nextjs, app-router, ui, midstream] | ||
| severity: minor |
Contributor
There was a problem hiding this comment.
The metadata for rr-midstream-nextjs-app-router-boundary-001 in the registry is inconsistent with its definition in skills/midstream/community/rr-midstream-nextjs-app-router-boundary-001/SKILL.md. Specifically, the name, tags, and severity fields do not match. Please align these fields to ensure the registry accurately reflects the skill's metadata.
name: 'Next.js App Router Client/Server Boundary'
path: skills/midstream/community/rr-midstream-nextjs-app-router-boundary-001/SKILL.md
category: midstream
phase: midstream
tags: [community, nextjs, midstream, react]
severity: major
Contributor
PlanGate Review
PlanGate review decision: pass
ポリシー: critical=fail / major=fail-if-required (warn) / minor=comment-only / info=skipped — spec: |
4 tasks
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
1 participant
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
PR 2 of 3 in the retrospective follow-up (foundation: #898). Implement S3: surface the community tier in
skills/registry.yamlwith explicitrecommended: false. Until now community skills were loaded at runtime but invisible in the catalog, which Codex flagged in the multi-perspective review as a scaling risk.What changed
Add a new "Community Skills (Experimental)" subsection between the core midstream block and the downstream block. Six skills listed:
rr-midstream-a11y-accessible-name-001rr-midstream-nextjs-app-router-boundary-001rr-midstream-modern-web-semantic-001rr-midstream-modern-web-performance-001rr-midstream-modern-web-browser-compat-001rr-midstream-modern-web-a11y-interactive-001All six carry
recommended: false. The section also carries a header comment defining the convention: a community skill becomes arecommended: truecandidate when it gains good/bad fixtures + golden output (the S1 follow-up).Test plan
node scripts/validate-meta-consistency.mjs→ "Meta consistency: OK"npm run skills:validate→ all SKILL.md validnpm test→ 1087/1087 greenRefs
docs/development/retrospectives/2026-05-21-25.md— S3 entry in the priority table.🤖 Generated with Claude Code