---
name: reproduce-bug
description: "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."
title: reproduce-bug
canonical_url: https://skilld.dev/gh/vercel/board/reproduce-bug
last_updated: 2026-11-19T06:15:42.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install vercel/board/reproduce-bug`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/reproduce-bug`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/vercel/board/reproduce-bug) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/reproduce-bug`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/reproduce-bug --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/reproduce-bug --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# 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.
