mirror of
https://github.com/supabase/supabase.git
synced 2026-10-06 09:55:06 +03:00
Raúl Barroso
01958e520f
## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES ## What kind of change does this PR introduce? Adds regression tests for something we noticed today. AI skills weren't being loaded on https://supabase.com/docs/guides/ai-tools/ai-skills, so while we fixed it, we wanted to make sure we could identify this faster. ## What is the current behavior? Less tests. AI skills loading and not ## What is the new behavior? Two tests, no new workflows — both ride existing CI: - **Unit test** (`AiSkills.utils.test.ts`) mocks GitHub, checks the parsing/shaping logic (dir filtering, frontmatter, install command, sorting, empty→fallback). Runs on every PR. - **Smoke test** (`AiSkillsIndex.smoke.test.ts`) hits the live page and asserts the skills table actually rendered. Runs in the daily docs smoke job, and can be pointed at any environment via `DOCS_SMOKE_URL`. Small supporting change: `getAiSkillsImpl` is now exported so the unit test can call it directly. ## Additional Context - Fixes https://linear.app/supabase/issue/AI-915/skills-docs-page-fails-to-load-available-skills <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Tests** * Added coverage for AI Skills loading, including directory filtering, metadata parsing, install command generation, fallback descriptions, and error handling. * Added a smoke test confirming the AI Skills documentation page loads successfully and displays install commands. * **Refactor** * Made AI Skills loading functionality accessible for direct testing while preserving existing behavior. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Reference Docs
Supabase Reference Docs
Maintainers
If you are a maintainer of any tools in the Supabase ecosystem, you can use this site to provide documentation for the tools & libraries that you maintain.
DocSpec
We use documentation specifications which can be used to generate human-readable docs.
- OpenAPI: for documenting API endpoints.
- SDKSpec (custom to Supabase): for SDKs and client libraries.
- ConfigSpec (custom to Supabase): for configuration options.
- CLISpec (custom to Supabase): for CLI commands and usage.
The benefit of using custom specifications is that we can generate many other types from a strict schema (eg, HTML and manpages). It also means that we can switch to any documentation system we want. On this site we use Next.js, but on Supabase's official website, we use a custom React site and expose only a subset of the available API for each tool.
Contributing
To contribute to docs, see the developers' guide and contributing guide.