base

Enforce TDD workflow, coding standards, and atomic todo management.

31|1|Updated Feb 12, 2026

Search Tags:#code quality #testing #tdd #software engineering #development workflow #refactoring

Ready to run

npx skills add https://github.com/Pouzor/pilotarr --skill base-pouzor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: base
Source: https://github.com/Pouzor/pilotarr/tree/main/.claude/skills/base
Command: npx skills add https://github.com/Pouzor/pilotarr --skill base-pouzor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces strict coding standards, TDD workflows, and quality gates to ensure maintainable, robust, and secure software development.

Core Features & Use Cases

Enforces Simplicity Rules: Strict limits on function/file size, nesting, and complexity.
Mandates TDD: Ensures tests are written first (RED), then code (GREEN), followed by validation.
Bug Fix Workflow: Guarantees bugs are fixed using TDD, preventing regressions.
Use Case: When developing a new feature, this Skill ensures all code adheres to best practices, is thoroughly tested before merging, and follows a defined, high-quality development process.

Quick Start

Follow the TDD workflow to implement the new feature.

Frequently Asked Questions about base

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

FAQPage Schema

How do I enforce strict TDD workflow and code quality limits during feature development?▼

To enforce TDD workflow and code quality, you must write failing tests first (RED), implement the minimum code to pass (GREEN), and validate against architectural and complexity limits. This guarantees maintainable features through strict quality gates before merging.

What is the best way to fix bugs without introducing regressions in software engineering?▼

The best way to fix bugs without regressions is to follow a strict Test-Driven Development cycle. You must first write a test that reproduces the bug, then fix the code to make it pass, ensuring the original error is resolved without breaking existing functionality.

Why does enforcing function size and architectural patterns matter for code refactoring?▼

Enforcing function size and architectural patterns during code refactoring prevents complexity and nesting from growing unchecked. It governs structural integrity, limits file complexity, and ensures the refactored codebase remains maintainable and adheres to universal development standards.

Can I use atomic todo management alongside TDD for new feature development?▼

Yes, atomic todo management is integrated directly alongside TDD for new feature development. It tracks session checkpoints and quality gates, ensuring that every test-driven development cycle step is completed and validated before moving to the next task.

Does strict test-driven development slow down the development workflow?▼

Strict test-driven development enforces a RED-GREEN validation cycle and quality gates that may initially slow down writing code, but it fundamentally prevents regressions and reduces debugging time. This ensures robust, secure software with a maintainable development workflow.