lfe-tdd

Automate red-green-refactoring with Python test execution and code analysis.

43|2|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/StChiotis/Library-First-Engineering --skill lfe-tdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lfe-tdd
Source: https://github.com/StChiotis/Library-First-Engineering/tree/main/.agents/skills/lfe-tdd
Command: npx skills add https://github.com/StChiotis/Library-First-Engineering --skill lfe-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures code quality and integrity by implementing a red-green-refactor process, verifying the Builder's implementation through automated testing.

Core Features & Use Cases

  • Automated Testing: Executes tests on the Builder's code to validate functionality.
  • Refactoring: Guides the Builder through refactoring steps to improve code quality.
  • Use Case: After the Builder completes implementation, this Skill runs tests to ensure the code meets quality standards before moving to the next phase.

Quick Start

Run the TDD skill to perform a quality pass on the code the Builder just wrote.

Frequently Asked Questions about lfe-tdd

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

FAQPage Schema
How do I automate red-green-refactoring to verify Builder code quality?

Automating red-green-refactoring involves executing Python scripts to run automated tests on the Builder's code, validating its functionality and ensuring adherence to best practices before moving to the next phase. This guarantees code quality and integrity.

What is the red-green-refactor process for code quality assurance?

The red-green-refactor process is a test-driven development technique that first writes failing tests, writes code to pass them, and then refactors the code. Automating this process ensures the Builder's implementation meets quality standards through continuous validation.

Do I need Python scripts to run automated testing in the Builder sub-pipeline?

Yes, Python scripts are required to execute tests and perform code analysis within the Builder sub-pipeline. These scripts automate the test execution phase, validating that the Builder's implementation passes quality checks before proceeding.

When should I run automated tests after the Builder completes implementation?

You should run automated tests immediately after the Builder completes its implementation. Performing this quality pass ensures the newly written code passes all tests and adheres to refactoring best practices before advancing to the next phase.

Can I use this to guide the Builder through refactoring steps?

Yes, this process guides the Builder through necessary refactoring steps to improve code quality. It automates the validation of functionality and ensures the implementation adheres to established best practices during the refactoring phase.