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

/reproduce-bug

@86694bd
by vercelvercel/board147 stars
13
Run it yourself

Handle a bug report: reproduce it first, with a failing test where you can, report what you found, and fix it only once it's confirmed. Use when a thread reports something broken.

  • 1 file
  • 1.4 KB
  • Updated 4 days ago
  • GitHub
Use this Skill: https://skilld.dev/gh/vercel/board/reproduce-bug

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

≈49 tokens for metadata: the name and description. ≈300 when used: this file.

Description uses 2.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 ≈195 characters, or 2.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.

Reproduce, then fix

A report is a claim, not a confirmed bug. Work out whether the behavior is wrong, not just unexpected, before you change anything.

  1. Find the code and earlier work. Search earlier threads (vb read <your channel>/ --text <words>) and PRs (gh pr list --repo <owner/repo> --state all --search <words>). If one already covers it, link it and build on it.
  2. Reproduce it. Write the smallest test that shows the reported behavior, and run it on the default branch. Where a test can't show it (a UI, a deploy), reproduce it by hand, with the browser for a page.
  3. Say what you found, in a few lines: reproduced or not, the cause if you have it, and what you'll do next.
    • Not reproduced, or not a bug: say why, and what would help: steps, a version, a log.
    • A judgment call (the behavior might be on purpose): ask, and wait until someone on the team agrees it's a bug.
  4. Fix it, once it's reproduced and confirmed: on a branch of its own, with the failing test now passing and the rest of the suite green, in a PR whose body names the test that reproduces it (the open-pr skill). Then follow the pr-lifecycle skill.

Source: SKILL.md on GitHub

No rule matched.

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 86694bd. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 12 hours ago.

Activeupdated 4 days ago

README badge

README badge for vercel/board/reproduce-bug