Implement Tests

Enforce Test Driven Development practices across unit, integration, and feature tests.

Updated Jan 21, 2026
One-click install
npx skills add https://github.com/Row0902/agents --skill implement-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Implement Tests
Source: https://github.com/Row0902/agents/tree/main/.agent/skills/implement_tests
Command: npx skills add https://github.com/Row0902/agents --skill implement-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codebases often drift into untested functionality, making changes risky and time-consuming. Enforcing Test Driven Development (TDD) practices helps ensure tests accompany features and guard against regressions.

Core Features & Use Cases

  • TDD Cycle Guidance: Red, Green, Refactor workflow to structure development tightly around tests.
  • Test Structure Guidance: Establish mirrored test directories and consistent naming to align with source code.
  • Quality Assurance Use Case: Applies to new features, bug fixes, and refactors to ensure reliable, maintainable codebases.

Quick Start

Write a failing test first, then implement the code to pass it.

Frequently Asked Questions about Implement Tests

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

FAQPage Schema
How do I enforce Test Driven Development practices to maximize test coverage?

To enforce Test Driven Development, you apply the Red, Green, Refactor cycle by writing a failing test first, then implementing the code to pass it. This maintains full test coverage and prevents codebase drift into untested functionality.

What is the best way to structure unit tests and mocking guidelines for maintainable code?

The best way to structure unit tests is establishing mirrored test directories and consistent naming conventions that align directly with your source code. Maintaining these test structures ensures your test suite remains reliable and scalable across integration and feature tests.

Can I use TDD discipline for refactoring existing codebases and bug fixes?

Yes, you can apply TDD discipline to refactoring and bug fixes. Writing tests before or during implementation guards against regressions, ensuring your existing codebase remains reliable and maintainable when adding new features or modifying current functionality.

Why does my test coverage drop when adding new features without TDD?

Test coverage drops because codebases often drift into untested functionality when tests do not accompany features. Enforcing Test Driven Development practices ensures tests are written first, guarding against regressions and maintaining reliable coverage thresholds.

Do I need specific testing frameworks to apply TDD cycle guidance?

You do not need specific testing frameworks to apply TDD cycle guidance. The approach structures your development workflow tightly around tests using the Red, Green, Refactor cycle, applying universally across unit, integration, and feature tests.