Skip to content

ReproCut

Reduces a failing project to a minimal reproducible case.

Trims files in a safe copy and rechecks that the failure persists.

For
Engineering and developer experience teams
Engine
Rust · Python
Source code
Closed · shown during a pilot
Buying
Written, fixed-price pilot

What is ReproCut?

ReproCut is a closed-source tool that reduces a failing software project to the smallest case that still reproduces the failure. It trims files in a safe copy and reruns the verification command at every step to check that the failure is still the same one. It works on Cargo, Python and npm projects and has not yet been validated on an independent project.

18 files, the same failure, 3 files.

Working copy · your checkout is never touched

src/app.pysrc/config.pysrc/parser.pysrc/tokens.pysrc/cache.pysrc/cli.pysrc/report.pysrc/utils.pysrc/io.pysrc/models.pysrc/plugins.pysrc/logging.pytests/test_cli.pytests/test_parser.pytests/test_io.pytests/conftest.pypyproject.tomlREADME.md

Figures from the small onboarding project in the README (18 → 3 files, 24 evaluations, 3/3 verification); file names are illustrative. Not a large-project benchmark.

How it works

From the product's own documentation. Each number says where and on which version it was measured.

  1. It works on a copy

    Your checkout is never touched. Every attempt runs in a fresh snapshot.

  2. It proves the failure first

    No reduction starts until a baseline shows the failure is repeatable.

  3. It reduces piece by piece

    Candidate reductions are tried; one is kept only if the same failure persists.

  4. It verifies the result again

    The final case is published only after re-verification under the chosen policy, with evidence, an attempt log and an HTML report.

18 → 3 files
On a small example project: 24 candidate evaluations and 3/3 final verifications. Not a large-project benchmark.
Finds the test command
Discovers the verification command in Cargo, Python and npm projects.
Failure identity
Normalized diagnostics check that 'the same failure' really is the same failure.
Independent validation: none yet
That is what we say until it is validated on a third-party project.

Stack

  • Rust
  • Python
  • Cargo / pip / npm

What it does not claim

Results depend on the reliability of the verification command you supply.

Current boundary

Results depend on the reliability of the supplied verification command.

What a pilot covers

A sample starting scope. Final deliverables and acceptance criteria are fixed in the written proposal.

Question
What is the smallest case that still reproduces the failure?
Likely input
A safe project copy and a verification command
Deliverables
  • Reduced reproducible case
  • Verification record for each reduction
  • Starting package for root cause review
Send your problem

Before you decide

Can I buy this product today?

A paid pilot and setup proposal can be prepared. Scope, data access, deliverables, timeline and a fixed price are agreed in writing after a discovery call.

Why is there no price?

Data volume, integration and success criteria differ from job to job. After the call you get a fixed-price written proposal; no paid work starts without your approval.

Do I need to upload live data here?

No. This site has no file upload or accounts. Data access, retention and permissions are set only in the pilot agreement.

What is the first step?

Choose ReproCut in the form and describe the problem you need to solve. The data and pilot boundaries are then set together.