testing

Enforce Test-Driven Development cycles and quality gates across programming languages.

48|5|Updated Sep 16, 2025
One-click install
npx skills add https://github.com/shinpr/agentic-code --skill testing-shinpr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/shinpr/agentic-code/tree/main/.agents/skills/testing
Command: npx skills add https://github.com/shinpr/agentic-code --skill testing-shinpr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces a rigorous Test-Driven Development (TDD) process and establishes clear quality criteria for writing, testing, and verifying code, ensuring robustness and maintainability.

Core Features & Use Cases

  • TDD Enforcement: Guides the RED-GREEN-REFACTOR cycle for all code changes.
  • Quality Gates: Mandates comprehensive testing, build success, style compliance, and type safety.
  • Mocking Policy: Defines best practices for using mocks and stubs to isolate units.
  • Use Case: When implementing a new feature, this Skill ensures that tests are written first, code passes all tests and linters, and existing functionality remains unbroken.

Quick Start

Follow the TDD process to write a new unit test for the user authentication module.

Frequently Asked Questions about testing

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

FAQPage Schema
How do I enforce Test-Driven Development principles when writing TypeScript code with Vitest?

Test-Driven Development with Vitest is enforced by guiding the AI agent through the RED-GREEN-REFACTOR cycle, mandating test coverage, and specifying criteria for mock usage and test granularity to ensure robust TypeScript code.

What is the RED-GREEN-REFACTOR cycle for code verification and how does it work?

The RED-GREEN-REFACTOR cycle is a Test-Driven Development process where you write a failing test first, write code to pass it, then refactor while ensuring code passes all quality checks including builds, linting, and type safety.

What's the best way to structure mocking and stubs for unit test isolation?

The best way to structure mocking and stubs is to follow a defined mocking policy that establishes best practices for isolating units, ensuring tests remain granular and focused on the specific component being verified.

Does this TDD approach work for verifying existing functionality across multiple programming languages?

Yes, this TDD approach works across multiple programming languages by enforcing Test-Driven Development principles and code quality standards, ensuring existing functionality remains unbroken when implementing new features.

Why does my code need to pass linting and type safety checks before TDD completion?

Code must pass linting, type safety, and builds before completion because these are mandated quality gates within the Test-Driven Development cycle, ensuring maintainability and robustness across the entire codebase.