Vercel Composition Patterns
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
Safe workflow for editing exported symbols or public APIs. An agent skill from blackwell-systems/agent-lsp.
$ npx skills add blackwell-systems/agent-lsp --skill lsp-edit-export -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install blackwell-systems/agent-lsp lsp-edit-export --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/blackwell-systems/agent-lsp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/lsp-edit-export .claude/skills/lsp-edit-export && 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 "lsp-edit-export" agent skill from https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-edit-export into .claude/skills/lsp-edit-export/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lsp-edit-export", 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/blackwell-systems/agent-lsp/tree/main/skills/lsp-edit-exportType 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 blackwell-systems/agent-lsp --skill lsp-edit-export -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install blackwell-systems/agent-lsp lsp-edit-export --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/blackwell-systems/agent-lsp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/lsp-edit-export .agents/skills/lsp-edit-export && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "lsp-edit-export" agent skill from https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-edit-export into .agents/skills/lsp-edit-export/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lsp-edit-export", 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 blackwell-systems/agent-lsp --skill lsp-edit-export -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install blackwell-systems/agent-lsp lsp-edit-export --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/blackwell-systems/agent-lsp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/lsp-edit-export .cursor/skills/lsp-edit-export && 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 "lsp-edit-export" agent skill from https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-edit-export into .cursor/skills/lsp-edit-export/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lsp-edit-export", 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/blackwell-systems/agent-lsp.git --path skills/lsp-edit-export--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 blackwell-systems/agent-lsp --skill lsp-edit-export -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install blackwell-systems/agent-lsp lsp-edit-export --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/blackwell-systems/agent-lsp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/lsp-edit-export .gemini/skills/lsp-edit-export && 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 "lsp-edit-export" agent skill from https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-edit-export into .gemini/skills/lsp-edit-export/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lsp-edit-export", 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 blackwell-systems/agent-lsp lsp-edit-exportInstalls 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 blackwell-systems/agent-lsp --skill lsp-edit-export -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/blackwell-systems/agent-lsp.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/lsp-edit-export .github/skills/lsp-edit-export && 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 "lsp-edit-export" agent skill from https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-edit-export into .github/skills/lsp-edit-export/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lsp-edit-export", 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 blackwell-systems/agent-lsp --skill lsp-edit-export -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install blackwell-systems/agent-lsp lsp-edit-export --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/blackwell-systems/agent-lsp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/lsp-edit-export .opencode/skills/lsp-edit-export && 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 "lsp-edit-export" agent skill from https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-edit-export into .opencode/skills/lsp-edit-export/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lsp-edit-export", 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.
lsp-edit-exportSafe workflow for editing exported symbols or public APIs. An agent skill from blackwell-systems/agent-lsp.
Lsp Edit Export is an agent skill from blackwell-systems/agent-lsp. Safe workflow for editing exported symbols or public APIs. Use when changing a function signature, modifying a public type, or altering any symbol used outside its own package — finds all callers first so nothing breaks silently.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/patterns.md`). Compatibility notes: Requires the agent-lsp MCP server (github.com/blackwell-systems/agent-lsp)
It sits in Development. The repository describes itself as: MCP server that orchestrates language servers into agent-native workflows. 65 tools, 30 CI-verified languages. The licence is MIT.
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 6fa5faf. 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:
mcp__lsp__go_to_symbolmcp__lsp__open_documentmcp__lsp__find_referencesmcp__lsp__get_diagnosticsmcp__lsp__run_buildmcp__lsp__replace_symbol_bodyEditWriteFrom allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From 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.
Requires the agent-lsp MCP server (github.com/blackwell-systems/agent-lsp)
From compatibility in the SKILL.md frontmatter.
Lsp Edit Export loads about 1.9k tokens when it runs, and up to ~2.4k if it reads all its reference files. Until then it costs about 61 tokens; SKILL.md has 713 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 found no risky patterns in SKILL.md.
Automated 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.
The full file from blackwell-systems/agent-lsp at commit 6fa5faf, republished under its MIT licence (© blackwell-systems). 713 words, ~1,856 tokens.
.claude/skills/lsp-edit-export/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Requires the agent-lsp MCP server.
Safe workflow for editing exported symbols. Always discovers all callers before touching any code, then verifies the change is clean.
Use this skill whenever you intend to change the signature, name, or behavior of an exported symbol: a symbol visible outside its defining package or module.
Language-specific definitions:
| Language | Exported means... |
|---|---|
| Go | Identifier starts with an uppercase letter (e.g. MyFunc, MyType) |
| TypeScript | Has export keyword; or is a public class member (no private) |
| Python | Not prefixed with _; or explicitly listed in __all__ |
| Java/C# | Has public or protected visibility modifier |
| Rust | Has pub keyword |
If you are unsure whether a symbol is exported, treat it as exported and run this workflow anyway. The cost is a few extra tool calls; the benefit is never breaking a hidden caller.
Do NOT skip this workflow even when you believe there are zero callers. The confirmation gate in step 3 exists precisely for that case.
If LSP is not yet initialized, call mcp__lsp__start_lsp with the
workspace root first. (agent-lsp supports auto-inference from file paths, so
explicit start is only required when switching workspaces or on a cold session.)
Use go_to_symbol to find the symbol's definition by name, without needing to
know its file path or line number in advance:
mcp__lsp__go_to_symbol({
"symbol_path": "PackageName.ExportedFunction",
"workspace_root": "/abs/path/to/repo" // optional, narrows scope
})symbol_path uses dot notation. For a top-level function Encode in package
codec, use "codec.Encode". For a method Reset on type Buffer, use
"Buffer.Reset". The last component is the leaf name; any prefix is used to
disambiguate when multiple symbols share the same leaf.
The tool returns a FormattedLocation with the definition file and 1-indexed
line/column. Record this position — you will need it in step 2.
Call find_references using the position_pattern field to express the cursor
position as a readable text pattern rather than raw coordinates. The @@ marker
indicates exactly where the cursor sits (the character immediately after @@):
mcp__lsp__find_references({
"file_path": "<definition file from step 1>",
"position_pattern": "func @@ExportedFunction(",
"include_declaration": false
})The @@ must immediately precede the first character of the symbol name.
Examples:
"func @@Encode(" — Go function declaration"type @@Buffer struct" — Go type declaration"export function @@parse(" — TypeScript function"class @@Parser:" — Python class"pub fn @@process(" — Rust functionIf position_pattern is unavailable on your MCP client, fall back to the
line and column fields from the location returned in step 1.
The tool returns a list of reference locations across the codebase.
Before making any change, present the impact summary to the user and ask for explicit confirmation. This gate is mandatory even when the caller count is zero.
Format the gate as follows:
## Impact Check: <SymbolName>
- Definition: <file>:<line>
- Callers found: N reference(s) in M file(s)
Files with callers:
- <file1>
- <file2>
...
Proceed with the edit? [y/n]If the user answers n, stop. Do not make any edits.
If the user answers y, proceed to step 4.
Why this gate exists even for 0 callers: the LSP index may be incomplete (e.g. files not yet saved, workspace not fully loaded). Zero callers is a data point, not a guarantee.
Apply your intended change using Edit or Write. When replacing a complete
function or method body, replace_symbol_body is an option that resolves the
symbol by name and replaces its full range without position math:
mcp__lsp__replace_symbol_body({
"file_path": "<definition file>",
"symbol_path": "ExportedFunction",
"new_body": "<new full definition>"
})For other edits (signature changes, partial modifications), use Edit or Write.
Follow the standard edit workflow for the language. If renaming, update all call
sites identified in step 2 as well; do not leave broken callers.
Collect diagnostics before the edit so you have a baseline for comparison in step 5:
mcp__lsp__get_diagnostics({
"file_path": "<definition file>"
})Then apply the edit and collect diagnostics again after.
Compare before and after diagnostic snapshots using the format in references/patterns.md.
If new errors appear, fix them before proceeding. Do not run the build with known diagnostic errors outstanding.
mcp__lsp__run_build({
"workspace_root": "/abs/path/to/repo"
})A clean build confirms no compilation errors across all affected packages. If the build fails, diagnose using the error output and diagnostic data from step 5. Fix and re-run until the build passes.
Emit the final output block:
## Edit Summary
- Symbol: <name> (<kind>)
- Callers found: N in M files
- Diagnostics: net +N/-N
- Build: PASSED / FAILEDIf build is FAILED, include the first 3–5 error lines and a brief diagnosis.
Goal: rename exported function `ParseConfig` → `LoadConfig` in pkg/config
Step 1 — go_to_symbol: symbol_path="config.ParseConfig"
→ pkg/config/parser.go:42:6
Step 2 — find_references: position_pattern="func @@ParseConfig("
→ 7 references in 4 files
Step 3 — gate:
## Impact Check: ParseConfig
- Definition: pkg/config/parser.go:42
- Callers found: 7 in 4 files
Files: cmd/main.go, internal/app.go, internal/loader.go, pkg/config/parser_test.go
Proceed? [y/n] → y
Step 4 — edit: rename declaration + all 7 call sites
Step 5 — diagnostics: net 0 (no new errors)
Step 6 — build: PASSED
Step 7 — report:
## Edit Summary
- Symbol: LoadConfig (function)
- Callers found: 7 in 4 files
- Diagnostics: net 0
- Build: PASSEDposition_pattern with @@ is a agent-lsp extension. If your MCP client
or server does not support it, fall back to explicit line and column
parameters from the location returned by go_to_symbol in step 1.
© blackwell-systems, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file (references) in skills/lsp-edit-export of blackwell-systems/agent-lsp.
Open the folder on GitHubat commit 6fa5faf
Lsp Edit Export 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 |
|---|---|---|---|---|---|---|
| Lsp Edit Export this skillblackwell-systems/agent-lsp | 159 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Vercel Composition Patternssupabase/supabase | 111k | 59 repos | ~726 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 25 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT |
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
blackwell-systems/agent-lsp
Enumerate exported symbols in a file and surface those with zero references across the workspace.
blackwell-systems/agent-lsp
Apply available quick-fix code actions for all current diagnostics in a file, one at a time with re-collection between each fix.
blackwell-systems/agent-lsp
Trigger language server code generation — implement interface stubs, generate test skeletons, add missing methods, generate mock types.
blackwell-systems/agent-lsp
Blast-radius analysis for a symbol or file — shows all callers, type supertypes/subtypes, and reference count before you change it.
blackwell-systems/agent-lsp
Two-phase safe rename across the entire workspace. An agent skill from blackwell-systems/agent-lsp.
blackwell-systems/agent-lsp
Speculative code editing session — simulate changes in memory before touching disk.
Categories
Safe workflow for editing exported symbols or public APIs. An agent skill from blackwell-systems/agent-lsp. Lsp Edit Export is an agent skill from blackwell-systems/agent-lsp. Safe workflow for editing exported symbols or public APIs.
Lsp Edit Export fits situations like: changing a function signature; modifying a public type; altering any symbol used outside its own package — finds all callers first so nothing breaks silently.
Run `npx skills add blackwell-systems/agent-lsp --skill lsp-edit-export -a claude-code`. Or copy the skill folder (skills/lsp-edit-export in blackwell-systems/agent-lsp) into .claude/skills/lsp-edit-export in your project. Claude Code loads it when a task matches its description.
Run `npx skills add blackwell-systems/agent-lsp --skill lsp-edit-export -a codex`. Or copy the skill folder (skills/lsp-edit-export in blackwell-systems/agent-lsp) into .agents/skills/lsp-edit-export 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 blackwell-systems/agent-lsp --skill lsp-edit-export -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lsp-edit-export, .gemini/skills/lsp-edit-export, .github/skills/lsp-edit-export and .opencode/skills/lsp-edit-export in your project.
SKILL.md names no scripts, command-line tools or credentials: Lsp Edit Export is instructions for the agent only. Our summary lists: Python 3. Its frontmatter pre-approves these tools: mcp__lsp__go_to_symbol, mcp__lsp__open_document, mcp__lsp__find_references, mcp__lsp__get_diagnostics, mcp__lsp__run_build, mcp__lsp__replace_symbol_body, Edit, Write. Compatibility (from SKILL.md): Requires the agent-lsp MCP server (github.com/blackwell-systems/agent-lsp).
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Lsp Edit Export is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.9k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 499 tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Lsp Edit Export: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
blackwell-systems (a GitHub user) maintains it in blackwell-systems/agent-lsp, which has 159 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on October 7, 2026.
Source: blackwell-systems/agent-lsp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.