skills.rest
MGPowerlytics
MGPowerlyticsCOMMUNITY
Explore all skills by this author →
GitHub

test-driven-development

Implement test-driven development workflows with pytest for betting platforms.

Updated Jan 16, 2026
Search Tags:#pytest#test-driven development#docker-compose#software-engineering#betting-system#elo-refactoring
One-click install
npx skills add https://github.com/MGPowerlytics/nhlstats --skill test-driven-development-mgpowerlytics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/MGPowerlytics/nhlstats/tree/main/.github/skills/test-driven-development
Command: npx skills add https://github.com/MGPowerlytics/nhlstats --skill test-driven-development-mgpowerlytics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill codifies a Test-Driven Development workflow for a betting system, driving quality by requiring tests before implementation and reducing defects across features.

Core Features & Use Cases

  • Red-Green-Refactor workflow: enforces rapid feedback loops and stable code through disciplined refactoring.
  • Test-first development: specifies features via tests before coding to ensure correct behavior from the start.
  • Unified Elo refactoring patterns: supports cross-sport refactoring and backward compatibility through a consistent base approach.

Quick Start

Start by writing a failing test for the next feature, implement the minimal code to satisfy the test, run the full suite with pytest, and redeploy the environment with Docker Compose when needed.

Frequently Asked Questions about test-driven-development

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

FAQPage Schema
How do I apply test-driven development to a betting system?▼

Test-driven development for a betting system uses Red-Green-Refactor cycles to write failing tests first, implement minimal code to pass, and refactor safely. This workflow reduces defects and drives quality across betting platform features.

What is the Red-Green-Refactor workflow in test-first development?▼

The Red-Green-Refactor workflow in test-first development specifies features via failing tests, implements minimal code to satisfy tests, and refactors safely. Running the full suite with pytest maintains rapid feedback loops and stable code.

Can I run pytest test suites with Docker Compose for betting platforms?▼

Yes, you can run pytest test suites and redeploy the betting platform environment with Docker Compose. This ensures deployment and documentation artifacts are maintained while validating incremental feature implementations through the test suite.

How do I refactor Elo rating systems across multiple sports?▼

Unified Elo refactoring across sports uses a consistent base approach to support cross-sport refactoring and backward compatibility. This test-driven pattern ensures rating logic remains stable while expanding betting system features.

What is the best way to start writing tests before implementation?▼

The best way to start test-first development is writing a failing test for the next feature, implementing minimal code to satisfy the test, running the full suite with pytest, and redeploying with Docker Compose when needed.

Does test-driven development reduce defects in betting platform features?▼

Test-driven development reduces defects across betting platform features by requiring tests before implementation. Codifying this TDD workflow enforces rapid feedback loops and stable code through disciplined refactoring.

Related Skills

Explore More Software Engineering Skills→
sabyunreposabyunrepo

arch-infra

Manage Docker Compose infrastructure and environment variables for local and production deployments.

Community
Intermediate
MGPowerlyticsMGPowerlytics

adding-new-sport

Add a new sport to the betting system with a unified Elo rating interface and data pipelines.

Community
Advanced
p1tl0rdp1tl0rd
8

tdd-ros2

Establish test-first workflows for ROS 2 nodes using gtest and pytest.

Community
Advanced
BryceRoberts13BryceRoberts13

test-driven-development

Enforce a test-first RED-GREEN-REFACTOR workflow for feature and bugfix implementation.

Community
Advanced