tdd-assertions

Detect and repair weak test assertions across Rust, Python, TypeScript, Go, and Shell.

2|Updated Sep 12, 2016

Search Tags:#testing #tdd #python #rust #assertions #cross-language

Ready to run

npx skills add https://github.com/paulnsorensen/dotfiles --skill tdd-assertions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd-assertions
Source: https://github.com/paulnsorensen/dotfiles/tree/main/claude/skills/tdd-assertions
Command: npx skills add https://github.com/paulnsorensen/dotfiles --skill tdd-assertions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect and fix weak test assertions that AI generates across Rust, Python, TypeScript, Go, and Shell. Use this skill whenever you write or review tests, when the user says "strengthen assertions", "fix weak tests", or during /wreck, /fromage, and /simplify flows. Also use as a mental checklist before committing test code — AI assistants systematically produce assertions that pass when the code is broken, which is the cardinal sin of TDD. Trigger proactively on test generation and test review.

Core Features & Use Cases

Fix weak test assertions that pass when the code is broken.
Detect weak patterns across languages and frameworks.
Provide brief explanations for each fix and guidance for stronger checks.

Quick Start

Give a weak test snippet and ask for stronger assertions.

Frequently Asked Questions about tdd-assertions

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

FAQPage Schema

How do I fix weak test assertions that pass when code is broken?▼

Detecting weak test assertions involves identifying patterns that pass when code is broken, then substituting them with strong, verifiable checks. This skill works across Rust, Python, TypeScript, Go, and Shell to enforce high-quality assertions during test generation and review.

Why does my AI generated test suite pass even when the implementation is broken?▼

AI assistants systematically produce weak test assertions that pass when code is broken, which is the cardinal sin of TDD. This skill proactively triggers during test generation and review to identify weak patterns and replace them with verifiable assertions.

What's the best way to strengthen weak assertions across multiple programming languages?▼

Strengthening weak assertions across multiple languages requires a cross-language detection tool covering Rust, Python, TypeScript, Go, and Shell. This skill identifies weak patterns and substitutes them with strong, verifiable assertions while providing explanations for each fix.

Does this assertion repair skill support Go and Shell test frameworks?▼

Yes, this skill supports Go and Shell test frameworks alongside Rust, Python, and TypeScript. It detects and repairs weak assertions across all five languages, ensuring tests fail appropriately when code is broken during test generation, review, and pre-commit flows.

How do I integrate assertion checking into my pre-commit workflow?▼

Integrate assertion checking into pre-commit flows by triggering this skill as a mental checklist before committing test code. It detects weak patterns, substitutes strong verifiable assertions, and provides concise explanations for each change during pre-commit, test generation, and review flows.

When should I not use automated assertion strengthening for my tests?▼

Review each suggested change rather than blindly applying automated fixes, as this skill provides concise explanations for every substitution to ensure the strong, verifiable assertion fits your specific testing context, language, and framework requirements across Rust, Python, TypeScript, Go, and Shell.