Test Writer
MANDATORY - INVOKE BEFORE writing ANY test code (def test_*, class Test*). Prevents brittle tests. Read this skill first, then write tests.
Install
/plugin marketplace add Freddy-CHEN-ux/00_claude_skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Freddy-CHEN-ux/00_claude_skills --skill test-writergit clone --depth 1 https://github.com/Freddy-CHEN-ux/00_claude_skills.git /tmp/00_claude_skills
mkdir -p ~/.claude/skills
cp -r /tmp/00_claude_skills/skills/test-writer ~/.claude/skills/test-writerPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# test-writer Skill ## 🚨 CRITICAL: MANDATORY FOR ALL TEST WRITING AND UPDATING **YOU CANNOT WRITE OR UPDATE TESTS WITHOUT THIS SKILL.** If you write or update tests without following this skill, you will: - Write brittle tests with hardcoded library outputs - Create self-evident tests that provide zero value - Use fixtures incorrectly (overuse for simple cases, underuse for complex) - Test Python/library behavior instead of YOUR code's contracts **This skill is your checklist. Follow it step-by-step. No shortcuts.** --- ## 🚨 CRITICAL FOR TEST WRITING - **BEFORE writing tests** → Use test-writer skill (MANDATORY - analyzes code type, dependencies, contract) - **AFTER writing tests** → Invoke pytest-test-reviewer agent (validates patterns) - **YOU CANNOT WRITE TESTS WITHOUT test-writer SKILL** - No exceptions, no shortcuts, every test, every time --- ## When to Use This Skill Use this skill when: - ✅ User asks "write tests for X" - ✅ You're creating a new test file (`test_*.py`) - ✅ You're adding tests to an existing test file - ✅ User says "test this" or "add test coverage" - ✅ You've just written code and need to test it - ✅ **You're updating/modifying existing tests** (e.g., when test-fixer needs to update test expectations) - ✅ **Tests are failing and need to be fixed** (use this skill to understand what to change) **DO NOT write or update tests without using this skill. PERIOD.** --- ## 🔄 How This Skill Interacts With Other Skills
Details
- Skill name
test-writer- Repository
- Freddy-CHEN-ux/00_claude_skills
- Path
skills/test-writer/SKILL.md- Repo updated
- 10 January 2026
FAQ
What does the Test Writer skill do?
MANDATORY - INVOKE BEFORE writing ANY test code (def test_*, class Test*). Prevents brittle tests. Read this skill first, then write tests.
How do I install the Test Writer skill?
Claude Code plugin: /plugin marketplace add Freddy-CHEN-ux/00_claude_skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Test Writer popular?
It lives in Freddy-CHEN-ux/00_claude_skills, which has 8 GitHub stars and 3 forks.
Related skills
Add Integration
8Freddy-CHEN-ux/00_claude_skills
Build a new API integration for Nexus. Load when user mentions "add integration", "new integration", "integrate with", "connect to [service]", or "build [service] integration". Interactive workflow that discovers API endpoints, plans the integration, and creates a project for implementation.
AI Agents
8Freddy-CHEN-ux/00_claude_skills
Production-grade AI agent patterns with MCP integration, agentic RAG, handoff orchestration, multi-layer guardrails, and observability (modern best practices)
AI LLM
8Freddy-CHEN-ux/00_claude_skills
Production LLM engineering skill. Covers strategy selection (prompting vs RAG vs fine-tuning), dataset design, PEFT/LoRA, evaluation workflows, deployment handoff to inference serving, and lifecycle operations with cost/safety controls.
Testing
8Freddy-CHEN-ux/00_claude_skills
Run tests before and after changes. Only add tests for complex logic, not boilerplate. Database tests matter most.
Test Voice Report
8Freddy-CHEN-ux/00_claude_skills
Test report generation with TEXT transcripts (NOT real calls). For real Twilio calls, use twilio-test-call instead.
Testing Anti Patterns
8Freddy-CHEN-ux/00_claude_skills
Use to avoid critical testing mistakes. Five Iron Laws: Never test mock behavior, Never add test-only methods, Never mock without understanding, Always integration test, Always test error paths.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.