testing-discipline

Name: testing-discipline
Availability: InStock
Author: sobhan

Enforce test-first development with regression tests for bug fixes and refactorings.

1|Updated May 12, 2026

Search Tags:#code quality #refactoring #bug fixing #test-driven development #test-first

Ready to run

npx skills add https://github.com/sobhanashine/nazarato --skill testing-discipline-sobhanashine

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: testing-discipline
Source: https://github.com/sobhanashine/nazarato/tree/main/.agents/skills/testing-discipline
Command: npx skills add https://github.com/sobhanashine/nazarato --skill testing-discipline-sobhanashine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the issue of skipping tests under pressure, which can lead to silent failures and technical debt.

Core Features & Use Cases

Test-First Development: Encourages writing tests before writing code to ensure code quality and maintainability.
Bug Fixing: Ensures that regression tests are written first for every bug fix, followed by the fix itself.
Refactoring: Requires that existing tests pass without changes to test bodies during refactoring.
UI Changes: Prompts for additional testing if UI changes are not accompanied by type-checking.

Quick Start

Apply the testing-discipline skill to your codebase to enforce test-first development practices.

Frequently Asked Questions about testing-discipline

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

FAQPage Schema

How do I enforce test-first development practices in my software workflow?▼

Test-first development is enforced by ensuring tests are written before code, regression tests precede bug fixes, and refactorings do not break existing tests. This maintains code quality and prevents silent failures caused by skipping tests under pressure.

What is the best way to prevent regressions when fixing bugs?▼

To prevent regressions during bug fixing, write a regression test for the specific bug first, followed by the fix itself. This ensures the original failure is captured and prevents future code changes from reintroducing the same defect.

How does test-driven development protect code during refactoring?▼

Test-driven development protects refactoring by requiring that existing tests pass without any changes to the test bodies. This verifies that internal structural changes preserve the original external behavior and prevent accidental feature breakage.

Can I use this to enforce testing for UI changes that lack type-checking?▼

Yes, it applies to UI changes by prompting for additional testing if the UI changes are not accompanied by type-checking. This ensures that interface modifications receive proper verification to maintain overall codebase stability.

Why should I write tests before code instead of after?▼

Writing tests before code ensures the test accurately captures requirements before implementation begins. This test-first approach prevents technical debt, avoids silent failures common under delivery pressure, and guarantees the resulting code is maintainable.