skills.rest
hellowind777
hellowind777COMMUNITY
Explore all skills by this author →
GitHub

hello-test

Enforces TDD red-green-refactor workflow and test coverage standards for code changes.

702|99|Updated Sep 26, 2025
Search Tags:#TDD#test coverage#Jest#Testing#RED-GREEN-REFACTOR#PyTest#Unit Tests
One-click install
npx skills add https://github.com/hellowind777/helloagents --skill hello-test
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hello-test
Source: https://github.com/hellowind777/helloagents/tree/main/skills/hello-test
Command: npx skills add https://github.com/hellowind777/helloagents --skill hello-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often write tests after implementation, skip edge cases, or produce brittle tests coupled to internal details. This Skill enforces a disciplined test-first workflow so new features and bug fixes ship with meaningful, behavior-focused test coverage.

Core Features & Use Cases

  • Mandatory TDD Cycle: Enforces the red-green-refactor loop with vertical slicing—one behavior, one failing test, minimal implementation—before any production code is written.
  • Coverage Strategy: Defines required coverage tiers: unit tests for core logic, integration tests for API endpoints, E2E tests for critical user flows, and failing-test-first for bug fixes.
  • Test Quality Rules: Requires behavior-describing test names, AAA structure, independent tests, boundary case coverage (null, 0, -1, MAX_INT, error paths), and mocks only for external dependencies.
  • Use Case: When fixing a token validation bug, the Skill requires writing a failing test like "should reject expired tokens" first, confirming it fails, then implementing the minimal fix.

Quick Start

Ask the agent to implement a new feature or fix a bug using TDD with proper test coverage for the target module.

Frequently Asked Questions about hello-test

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

FAQPage Schema
How do I practice TDD when writing new features?▼

Follow the red-green-refactor cycle: write a failing test describing the expected behavior, write the minimal code to pass it, then refactor while keeping tests green. Work in vertical slices—one behavior at a time—rather than writing all tests upfront.

What test coverage is needed for APIs and core logic?▼

Core business logic requires unit tests, API endpoints need integration tests covering success and main failure paths, and critical user flows need E2E tests. Bug fixes must start with a failing test that reproduces the issue.

Should I mock internal modules in unit tests?▼

Mock only external dependencies like databases, APIs, and file systems—never the code under test itself. If you must mock internal collaborators, first evaluate whether the interface is too shallow or the test entry point is wrong.

When is it acceptable to skip writing tests first?▼

Exemptions apply to pure UI style changes without logic, config file modifications, documentation changes, and explicit rapid prototyping. Mark these cases with [-] and a reason; everything else requires tests before implementation.

Why do my tests break when I refactor internal code?▼

Tests break during refactoring when they are coupled to implementation details like private functions or internal call order. Write tests against public interfaces and observable behavior so they survive internal restructuring.

Related Skills

Explore More Software Engineering Skills→
chaimtchaimt

tdd-plan

Plan public interfaces and test priorities before coding with a TDD workflow.

Community
Intermediate
mlinnenmlinnen
1

release-validation-triage

Triage release readiness by re-running failing tests in isolation.

Community
Intermediate
Kidoz-SDKKidoz-SDK

typescript-review

Review TypeScript and JavaScript diffs for Metabase coding standards and style violations.

Official
Intermediate
baphledbaphled
1

prove-correctness

Generate executable tests to prove or disprove code property claims.

Community
Advanced