npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

codex-bug-reproducer

v0.2.0

Published

A consent-first Codex skill that finds likely bugs, proves them with tests, and verifies approved fixes.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

kappaemmekappaemme

Keywords

codexskilldebuggingbug-finderbug-huntingbug-reproductionregression-testtestingdeveloper-toolsred-green

Readme

Codex Bug Reproducer

A consent-first Codex skill that scans a codebase for likely bugs, ranks concrete candidates, and proves or rejects them with focused tests. It can also turn bug reports, stack traces, screenshots, and failing behavior into minimal reproducible cases, then prove approved fixes with red-to-green evidence.

You do not need to know the bug first. Bug Reproducer inspects contracts, boundaries, state transitions, error paths, and real callers to identify specific triggering cases. It never claims a bug from code inspection alone: a candidate becomes a proven bug only when an approved focused test fails for the predicted reason.

What it does

  • Finds likely correctness bugs without requiring a bug report
  • Ranks candidates by contract evidence, reachability, reproducibility, and impact
  • Shows the exact trigger, expected result, likely actual result, and source location
  • Requires approval before creating reproduction files
  • Builds focused deterministic tests for the strongest approved candidates
  • Rejects setup errors and unrelated failures as false reproductions
  • Isolates the root cause
  • Requires separate approval before changing production code
  • Captures the same targeted command before and after
  • Returns FIX_PROVEN, STILL_FAILING, NOT_REPRODUCED, or another honest evidence status
  • Creates a native Markdown report that opens directly in Codex

Installation

npx --yes codex-bug-reproducer@latest

This installs the skill into:

~/.codex/skills/bug-reproducer

Restart Codex after installation.

Usage

Open any project and call it directly:

Use $bug-reproducer to scan this codebase for likely bugs, rank the strongest candidates, and ask before creating tests or changing code.

You can also provide a known bug:

Use $bug-reproducer to investigate this bug: requesting page 1 skips the first results. Propose a minimal reproduction and wait for my approval before changing project files.

For discovery and tests without a production fix:

Use $bug-reproducer in reproduce-only mode to find and prove likely bugs in this project. Do not change production code.

Two approval gates

The first approval covers only the displayed candidate tests or reproduction harness. After a bug is proven, the skill explains the root cause and requests a separate approval for the exact production patch.

If the required files or approach change, it must stop and ask again. It cannot use a broad initial instruction as permission to modify the project.

Evidence labels

  • REPRODUCED
  • NOT_REPRODUCED
  • NO_BUG_PROVEN
  • INCONCLUSIVE
  • STILL_FAILING
  • FIX_UNVERIFIED
  • FIX_REGRESSION
  • FIX_PROVEN

Output

outputs/bug-reproducer-evidence.json
outputs/bug-reproducer-report.md

The report includes the original bug, expected versus actual behavior, minimal reproduction, root cause, approved files, red/green evidence, broader checks, limitations, and residual risks.

Manual installation

git clone https://github.com/Kappaemme-git/codex-bug-reproducer.git
mkdir -p ~/.codex/skills
cp -R codex-bug-reproducer/bug-reproducer ~/.codex/skills/bug-reproducer

Restart Codex after installation.

License

MIT