skills.rest
japurcell
japurcellCOMMUNITY
Explore all skills by this author →
GitHub

test

Guide failing-test-first TDD workflows with implementation and verification steps.

Updated Mar 19, 2026
Search Tags:#workflow#testing#tdd#development#bug-fix#prove-it
One-click install
npx skills add https://github.com/japurcell/skills --skill test-japurcell
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test
Source: https://github.com/japurcell/skills/tree/main/skills/test
Command: npx skills add https://github.com/japurcell/skills --skill test-japurcell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines development by enforcing a failing-test-first approach and guiding the subsequent implementation and verification.

Core Features & Use Cases

  • Fail-first tests: Prompt the creation of tests that fail initially to drive focused implementation.
  • Incremental implementation: Add the minimal code to satisfy tests, followed by refactoring for maintainability.
  • Prove-It bug fixes: Reproduce bugs with tests, validate fixes, and run regression checks to prevent regressions.
  • Browser-related workflows: Coordinate with browser testing as needed using the addy-browser-testing-with-devtools skill for MCP verification.

Quick Start

Run the TDD workflow by writing a failing test first, then implement the code to make it pass.

Frequently Asked Questions about test

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

FAQPage Schema
How do I start a TDD workflow for feature development?▼

Run a TDD workflow by first writing a test that fails to define expected behavior, then adding minimal implementation code to satisfy the test, and finally refactoring to maintain code quality while verifying all tests pass.

What is the best way to fix bugs using test-driven development?▼

Fix bugs using a Prove-It validation approach by first reproducing the bug with a failing test, implementing the code fix to make it pass, and running regression checks to prevent future regressions across the codebase.

Does this TDD workflow support browser testing and DevTools verification?▼

Browser-related TDD workflows are supported and can coordinate with browser testing using DevTools for MCP verification, allowing you to validate browser-specific issues and run Prove-It checks during development and bug fixes.

Can I use this for regression checks after implementing code changes?▼

Regression checks are fully supported after implementation; the workflow guides you through creating failing tests, adding code, and verifying changes to ensure new modifications do not break existing functionality across the codebase.

Do I need any dependencies or external scripts to run the TDD process?▼

No dependencies are required to run the TDD process, which specifies a structured, repeatable workflow with prompts for test creation, implementation, and verification, while supporting optional references or scripts for extension.

Related Skills

Explore More Software Engineering Skills→
sidtheonesidtheone
14

insight-sentinel

Generate failing test suites from plan intent to define behavior contracts.

Community
Advanced
btseytlinbtseytlin
47

test-driven-development

Implement deterministic code changes via failing tests before minimal production code.

Community
Intermediate
yutnayutna
2

nextjs-browser-qa

Automate browser QA checks for Next.js applications with Playwright-based tests.

Community
Advanced
romiluz13romiluz13
161

test-driven-development

Enforce the red-green-refactor TDD cycle with failing tests before production code.

Community
Intermediate