rcode-prove-it

Write failing tests before implementing JavaScript and TypeScript fixes.

2|1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/hanzlahabib/rcode --skill rcode-prove-it
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rcode-prove-it
Source: https://github.com/hanzlahabib/rcode/tree/main/rcode/skills/actions/4-implementation/rcode-prove-it
Command: npx skills add https://github.com/hanzlahabib/rcode --skill rcode-prove-it

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents brittle, guess-first development by making you prove a feature or bug fix with a failing test before changing code.

Core Features & Use Cases

  • Red-Green-Refactor Workflow: Start with a failing test, make the smallest change to pass, then clean up safely.
  • Bug Reproduction First: Capture the reported bug as an automated regression test before opening the implementation.
  • Test Runner Detection: Works with common JavaScript and TypeScript test setups such as Jest, Vitest, Playwright, and node:test.
  • Use Case: A login bug only happens for certain input characters; this Skill helps you reproduce it in a test, fix the code, and keep the regression covered.

Quick Start

Use the rcode-prove-it skill to write a failing test for the feature or bug you want to validate, then implement the smallest fix and refactor once the test passes.

Frequently Asked Questions about rcode-prove-it

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a failing test before fixing a JavaScript bug?

Test-driven development in TypeScript starts by writing a failing test that proves your feature or bug fix, making the smallest code change to turn the test green, and refactoring safely once the test passes.

Can I use test-driven development with Playwright and Vitest?

Yes, test-driven development works with Playwright and Vitest, along with Jest and node:test, automatically detecting your test runner to validate features and regression bugs across JavaScript and TypeScript workflows.

Why should I reproduce a regression bug as a failing test first?

Reproducing a regression bug as a failing test first prevents guess-first development by proving the issue exists before you change code, ensuring your implementation fix is verified and the regression remains covered.

What is the red green refactor workflow in JavaScript?

The red green refactor workflow in JavaScript is a test-driven development cycle where you write a failing test, make the smallest code change to pass it, and then clean up the implementation safely.

Does this test-driven development approach work for TypeScript projects?

Yes, this test-driven development approach works for TypeScript projects, applying the red green refactor cycle to validate new features and regression bugs across supported test runners like Jest and Vitest.