Index of every page on this site: llms.txt
All skills
vercel-labs avatar

/ui-sdk-expert-review

@fb6945a
by Vercel Labsvercel-labs/ui6.3k stars
218
Run it yourself

Reviews a change with ui-sdk's framework experts (react, vue, svelte, solid, web), only the ones the change reaches, each from its last reviewed commit. Use before merging a branch that touches an adapter, core, specs, examples or framework docs, or when asked for an expert review. Pass a base ref, framework names, or nothing.

  • 1 file
  • 2.7 KB
  • Updated 3 weeks ago
  • GitHub
Use this Skill: https://skilld.dev/gh/vercel-labs/ui/ui-sdk-expert-review

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈88 tokens for metadata: the name and description. ≈578 when used: this file.

Description uses 4.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈351 characters, or 4.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

ui-sdk: expert review

Run the framework experts on what changed. Each expert lives in .agents/experts/<framework>/: who it is in expert.md, what it knows in knowledge.md and what's decided in decisions.md. You orchestrate; the experts review.

1. Find the scope

node scripts/expert-scope.mjs --json            # each expert from its "Last reviewed" commit
node scripts/expert-scope.mjs --base origin/main --json   # a branch before merging

Arguments narrow it: a ref becomes --base; framework names keep only those experts. An empty plan means no expert is needed: say so and stop.

Then run each framework's own lint rules on what changed, so the experts spend their review on what a linter can't catch:

git diff --name-only <base>...HEAD | xargs npx eslint --no-warn-ignored

2. Ask the experts

Spawn one background agent per framework in the plan, all at once, as <framework>-expert (in a harness without named agents, a general-purpose agent told to read .agents/experts/<framework>/expert.md first and act as it). Prompt:

Review mode. Scope: git diff <base>...HEAD.
Your files: <own>. Shared files every adapter renders: <shared>.
Review your files, and the shared ones only for what a user of your framework would meet.
Don't report anything decisions.md lists, or these lint findings: <findings, or none>.

Each expert works in its own worktree when it writes throwaway tests (git worktree add ../ui-sdk-expert-<framework> HEAD), with its own ports.

3. Collect

  1. One table: framework, verdict, proven findings by rank, suspected, revisit.
  2. Dedupe across experts: a finding in core that several experts report is one item, listed once, with every framework it reaches.
  3. Hand the table to the user. Don't fix anything unless asked.

4. After triage

Each finding goes one of three ways, in the same turn:

  • Fix now: fix it with its proof as the test.
  • Later: one line under "Known and open" in that expert's decisions.md.
  • Won't do / decided otherwise: one line under "Settled" in decisions.md, with the reason, so no expert raises it again.

Then move Last reviewed: in each expert's decisions.md to the reviewed HEAD. If an expert said its knowledge.md was wrong, fix the file and its "Last checked" date.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at fb6945a. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 14 hours ago.

Activeupdated 3 weeks ago
metadata
{
  "internal": true
}

README badge

README badge for vercel-labs/ui/ui-sdk-expert-review