test-writer

Enforce contract-first testing to prevent brittle unit, integration, and end-to-end tests.

6|1|Updated Mar 5, 2026

Search Tags:#qa #fixtures #unit-testing #integration-testing #contract-testing #test-writing

Ready to run

npx skills add https://github.com/pwv-vc/agentcribs-community --skill test-writer-pwv-vc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-writer
Source: https://github.com/pwv-vc/agentcribs-community/tree/main/resources/tearsheets/arsenal/dot-claude/skills/test-writer
Command: npx skills add https://github.com/pwv-vc/agentcribs-community --skill test-writer-pwv-vc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured, contract-first approach to testing, helping teams avoid brittle, self-evident tests and improper fixtures by focusing on YOUR code guarantees rather than library behavior.

Core Features & Use Cases

Contract-driven testing patterns that prioritize YOUR code's guarantees over library internals.
Guided fixture strategies and test-structure templates for unit, integration, and E2E workflows.
Integrated workflow from analysis to automated review, including coordination with pytest-test-reviewer.

Quick Start

Review this skill before writing tests and run pytest-test-reviewer after adding or updating tests.

Frequently Asked Questions about test-writer

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

FAQPage Schema

How do I prevent brittle unit tests from breaking on library updates?▼

To prevent brittle unit tests, enforce a contract-first approach that anchors test assertions to your code guarantees rather than third-party library behavior. This strategy ensures your tests validate your application logic without coupling to volatile library internals.

What is contract testing and when should I use it?▼

Contract testing is a structured approach validating that your code meets predefined guarantees. Use it across unit, integration, and end-to-end testing scenarios to avoid self-evident tests and improper fixtures by focusing on your code rather than library behavior.

How do I structure test fixtures for integration testing?▼

Structure integration testing fixtures using guided fixture strategies and test-structure templates provided by a contract-first workflow. These strategies prevent improper fixtures by anchoring test data to your code guarantees, ensuring maintainable and robust test suites.

Does this contract-first testing approach work for end-to-end testing?▼

Yes, the contract-first testing approach applies to end-to-end testing scenarios. It uses structured analysis and review gates to enforce required workflow steps, documentation, and anti-pattern checks, ensuring robust and maintainable test suites across all testing layers.

What is the best way to review test code for anti-patterns?▼

The best way to review test code is through an integrated workflow that includes automated review gates. After writing tests with a contract-first approach, coordinate with pytest-test-reviewer to identify anti-patterns, enforce documentation, and validate that tests anchor to your code guarantees.

Why do my tests keep failing when I update dependencies?▼

Your tests keep failing because they are brittle and likely coupled to library behavior rather than your code guarantees. Enforce a contract-first testing approach with structured analysis and anti-pattern checks to anchor assertions to your application logic instead of library internals.