⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
repro
Reproduce a GitHub issue bug report. Takes a GitHub issue URL from a Sentry SDK repository, creates a self-contained reproduction, and opens a PR with backlink to the original issue.
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
repro
doesn't work on my machine
Description
This repository will serve as a collection of reproductions of bugs and issues for Sentry's SDK ecosystem.
Usage
The structure of this repository is <sdk-name>/<issue-number-or-descriptive-name>/. Each such directory contains a self-contained reproduction with instructions for the problem involved.
The best way to use this repository is with Claude Skills:
/repro - Reproduce from GitHub Issue
Use this skill when you have a GitHub issue URL:
/repro https://github.com/getsentry/sentry-ruby/issues/2842
This will automatically:
- Parse the GitHub issue
- Create a reproduction in
sentry-ruby/2842/ - Backlink to the original issue in a comment
/repro-description - Reproduce from Description
Use this skill when you have a bug description but no GitHub issue:
/repro-description The HTTP status code is reported as 500 but breadcrumbs show 404...
This will:
- Ask which SDK is affected
- Suggest a descriptive branch name
- Create a reproduction in
{sdk}/{descriptive-name}/ - Skip the backlink step (no issue to link to)
Example
From GitHub issue:
/repro https://github.com/getsentry/sentry-ruby/issues/2842
From description:
/repro-description Rails returns 404 but Sentry reports 500 in trace data
// HOW IT'S BUILT
KEY FILES