craft-discipline

Verify unit tests, static analysis, design rules, and conventional commit format.

8|2|Updated Apr 16, 2026

Search Tags:#code quality #tdd #development workflow #checkpoints #commit verification

Ready to run

npx skills add https://github.com/SebastienDegodez/skraft-plugin --skill craft-discipline

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: craft-discipline
Source: https://github.com/SebastienDegodez/skraft-plugin/tree/main/plugins/skills/craft-discipline
Command: npx skills add https://github.com/SebastienDegodez/skraft-plugin --skill craft-discipline

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides self-discipline checkpoints to ensure best practices in software development during the TDD phase and before committing, enhancing code quality and maintainability.

Core Features & Use Cases

TDD Checkpoints: 11 self-discipline checkpoints to enforce good TDD practices, including test coverage, code quality, and design rules.
Commit Verification: Enforces rules for code commits, such as passing unit tests, code formatting, and conventional commit messages.
Use Case: Before each commit, run this Skill to automatically verify that all checkpoints have passed, ensuring the code is in a state ready for review.

Quick Start

Execute the craft-discipline skill before each commit to verify all checkpoints are met.

Frequently Asked Questions about craft-discipline

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

FAQPage Schema

How do I automate TDD checkpoints before committing code?▼

Automate TDD checkpoints before committing code by running a skill that verifies unit tests, static analysis, and design rules. This enforces 11 self-discipline checkpoints to ensure test coverage and code quality are met prior to commit.

What is conventional commit verification and how does it work?▼

Conventional commit verification checks commit messages against standard formatting rules. It works by validating the commit format, ensuring unit tests pass, and confirming code formatting before allowing a commit to finalize.

How do I enforce code quality rules in an agile development workflow?▼

Enforce code quality rules in an agile development workflow by integrating automated checkpoints at TDD and commit stages. This verifies static analysis, test coverage, and design rules to maintain code maintainability before each review.

Can I run commit verification without any external dependencies?▼

Yes, you can run commit verification without external dependencies. The skill operates independently with internal scripts and references, requiring no additional modules to validate unit tests and conventional commit formats.

What are the limitations of automated TDD checkpoints?▼

The limitations of automated TDD checkpoints include focusing strictly on pre-commit validation of unit tests, static analysis, and conventional commit format, which may not cover broader architectural design or integration test flaws.