Repository navigation
docs(coverage): record the Svelte adoption and the Astro removal - #672
Conversation
The coverage matrix still listed SvelteKit as an open gap and Astro as covered. Since 7.0.0 the plugin bundles the Svelte team's best-practices skill and documentation server, and no longer bundles the Astro skill. The candidate table now states the decision on both Svelte skills: the best-practices skill is adopted, and the code writer is rejected because it runs an unpinned package on every call while the bundled server offers the same tools. Part of #652 Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@coderabbitai review |
Action performed
|
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
Tried as a reader of the overview, at
Review: CodeRabbit reviewed this head and generated no actionable comments. CI is green. 🤖 Generated with Claude Code |
Why
The skill coverage overview still listed SvelteKit as an open gap and Astro as covered. Both changed when the plugin started bundling the Svelte team's guidance and dropped the Astro skill, so the overview pointed agents and readers at the wrong state.
What
The overview now shows SvelteKit as covered and Astro as not bundled, with where to get the Astro skill when it is needed. It also records the decision on the two Svelte candidates: one adopted, one rejected because it downloads and runs unpinned code that the bundled documentation server already replaces.
Fixes #652
🤖 Generated with Claude Code