PR Bot Reviews
pgplex/pgconsole
Triage, verdict, and reply to automated PR review comments from GitHub Copilot and Greptile, then iterate until the bots have nothing left to say.
Create a new splinter lint — a SQL view that checks for a database anti-pattern.
$ npx skills add supabase/splinter --skill new-lint -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install supabase/splinter new-lint --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/supabase/splinter.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/new-lint .claude/skills/new-lint && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "new-lint" agent skill from https://github.com/supabase/splinter/tree/main/.claude/skills/new-lint into .claude/skills/new-lint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "new-lint", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/supabase/splinter/tree/main/.claude/skills/new-lintType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add supabase/splinter --skill new-lint -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install supabase/splinter new-lint --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/supabase/splinter.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/new-lint .agents/skills/new-lint && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "new-lint" agent skill from https://github.com/supabase/splinter/tree/main/.claude/skills/new-lint into .agents/skills/new-lint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "new-lint", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add supabase/splinter --skill new-lint -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install supabase/splinter new-lint --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/supabase/splinter.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/new-lint .cursor/skills/new-lint && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "new-lint" agent skill from https://github.com/supabase/splinter/tree/main/.claude/skills/new-lint into .cursor/skills/new-lint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "new-lint", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/supabase/splinter.git --path .claude/skills/new-lint--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add supabase/splinter --skill new-lint -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install supabase/splinter new-lint --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/supabase/splinter.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/new-lint .gemini/skills/new-lint && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "new-lint" agent skill from https://github.com/supabase/splinter/tree/main/.claude/skills/new-lint into .gemini/skills/new-lint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "new-lint", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install supabase/splinter new-lintInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add supabase/splinter --skill new-lint -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/supabase/splinter.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/new-lint .github/skills/new-lint && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "new-lint" agent skill from https://github.com/supabase/splinter/tree/main/.claude/skills/new-lint into .github/skills/new-lint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "new-lint", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add supabase/splinter --skill new-lint -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install supabase/splinter new-lint --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/supabase/splinter.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/new-lint .opencode/skills/new-lint && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "new-lint" agent skill from https://github.com/supabase/splinter/tree/main/.claude/skills/new-lint into .opencode/skills/new-lint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "new-lint", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
new-lintCreate a new splinter lint — a SQL view that checks for a database anti-pattern.
New Lint is an agent skill from supabase/splinter, published by the product's own GitHub organization. Create a new splinter lint — a SQL view that checks for a database anti-pattern. Use this skill when the user asks to add a lint, create a new check, implement a linting rule, or extend splinter with a new detection.
Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Linting and formatting. It works with SQL, Supabase and PostgreSQL. The repository describes itself as: Supabase Postgres Linter: Performance and Security Advisors.
9 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit fccca4b. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadEditWriteGlobGrepBashFrom allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
dockerdocker-composepythongitFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
supabase.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
New Lint loads about 2.9k tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 960 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Read, Edit, Write, Glob, Grep, BashAutomated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Without a licence we can't republish the file, so here is its outline and opening line. It has 960 words (~2,908 tokens).
“You are implementing a new lint for the splinter PostgreSQL linting tool. Follow every step in order. Do not skip steps.”
Just SKILL.md in .claude/skills/new-lint of supabase/splinter.
Open the folder on GitHubat commit fccca4b
New Lint next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| New Lint this skillsupabase/splinter | 280 | — | ~2.9k | Automated safety check: Notes | None | |
| PR Bot Reviewspgplex/pgconsole | 155 | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Requesting Code Reviewt1mmen/srtd | 105 | — | ~807 | Automated safety check: Pass | MIT | |
| Supabase Advanced Troubleshootingjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~2.8k | Automated safety check: Pass | MIT | |
| Diesel Guardayarotsky/diesel-guard | 121 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Srtd Devt1mmen/srtd | 105 | — | ~2.3k | Automated safety check: Pass | MIT |
pgplex/pgconsole
Triage, verdict, and reply to automated PR review comments from GitHub Copilot and Greptile, then iterate until the bots have nothing left to say.
t1mmen/srtd
Structured code review workflow for SRTD development. An agent skill from t1mmen/srtd.
jeremylongshore/tons-of-skills-marketplace
Deep Supabase diagnostics: pgstatstatements for slow queries, lock debugging with pglocks, connection leak detection, RLS policy conflicts, Edge Function cold starts, and Realtime connection drop…
ayarotsky/diesel-guard
Lints Diesel and SQLx Postgres migrations for unsafe schema changes that lock tables or cause downtime, and authors custom Rhai checks.
t1mmen/srtd
Expert knowledge for developing the SRTD codebase itself. An agent skill from t1mmen/srtd.
supabase/supabase
Write, review, and migrate Supabase logs queries against the ClickHouse-backed logs table (the logs.all.otel analytics endpoint).
Works with
Categories
Create a new splinter lint — a SQL view that checks for a database anti-pattern. New Lint is an agent skill from supabase/splinter, published by the product's own GitHub organization. Create a new splinter lint — a SQL view that checks for a database anti-pattern.
New Lint fits situations like: the user asks to add a lint; create a new check; implement a linting rule; extend splinter with a new detection.
Run `npx skills add supabase/splinter --skill new-lint -a claude-code`. Or copy the skill folder (.claude/skills/new-lint in supabase/splinter) into .claude/skills/new-lint in your project. Claude Code loads it when a task matches its description.
Run `npx skills add supabase/splinter --skill new-lint -a codex`. Or copy the skill folder (.claude/skills/new-lint in supabase/splinter) into .agents/skills/new-lint in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add supabase/splinter --skill new-lint -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/new-lint, .gemini/skills/new-lint, .github/skills/new-lint and .opencode/skills/new-lint in your project.
Going by SKILL.md and its folder, New Lint needs the command-line tools its instructions call (docker, docker-compose, python and git). Our summary lists: Python 3; Docker. Its frontmatter pre-approves these tools: Read, Edit, Write, Glob, Grep, Bash.
SKILL.md names 1 domain. In commands or code: supabase.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
No licence was found for New Lint or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
About 2.9k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with New Lint: PR Bot Reviews (pgplex/pgconsole, 155 stars), Requesting Code Review (t1mmen/srtd, 105 stars), Supabase Advanced Troubleshooting (jeremylongshore/tons-of-skills-marketplace, 2.8k stars) and Diesel Guard (ayarotsky/diesel-guard, 121 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
supabase (a GitHub organization, an official publisher) maintains it in supabase/splinter, which has 280 GitHub stars. The repository was last updated on September 29, 2026.
Source: supabase/splinter on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.