Testing

Run tests before and after changes. Only add tests for complex logic, not boilerplate. Database tests matter most.

8 stars 3 forksTesting & QA Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add Freddy-CHEN-ux/00_claude_skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Freddy-CHEN-ux/00_claude_skills --skill testing
Manual install
git 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/testing ~/.claude/skills/testing

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Testing

Verify changes don't break things. Don't create test bloat.

> **Announce:** "I'm running tests to verify the changes."

## Philosophy

**Database (pgTAP):** This is where real logic lives. Test it thoroughly.

**Frontend (Vitest):** Thin RPC layer. Only test:
- Complex transformations
- Non-obvious edge cases
- NOT: "does this call that function"

## Workflow

**Before implementing:**
```bash
bun run test
```
If tests fail, fix them first.

**After implementing:**
```bash
bun run test
```
If tests fail, your change broke something. Fix it.

## When to Add Tests

**YES - add tests for:**
- New database functions with business logic
- Complex data transformations
- Non-obvious edge cases you discovered

**NO - don't test:**
- "Does this function call that function"
- Pinia store initialization
- Vue component mounting
- API calls with mocked responses
- Obvious behavior readable from code

## Commands

```bash
bun run test        # All tests (unit + db)
bun run test:unit   # Frontend only
bun run test:db     # Database only (pgTAP)
```

## If Tests Fail

1. Read the error message
2. Check if YOUR change caused it
3. If yes → fix your code
4. If no → fix the test or report the issue
Read the full skill on GitHub

Details

Skill name
testing
Path
skills/testing/SKILL.md
Repo updated
10 January 2026

FAQ

What does the Testing skill do?

Run tests before and after changes. Only add tests for complex logic, not boilerplate. Database tests matter most.

How do I install the Testing 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 Testing popular?

It lives in Freddy-CHEN-ux/00_claude_skills, which has 8 GitHub stars and 3 forks.

Related skills

Add Integration

8

Freddy-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.

Software Development

AI Agents

8

Freddy-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, LLMs & Agents

AI LLM

8

Freddy-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.

AI, LLMs & Agents

Testing Anti Patterns

8

Freddy-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.

Testing & QA

Test Writer

8

Freddy-CHEN-ux/00_claude_skills

MANDATORY - INVOKE BEFORE writing ANY test code (def test_*, class Test*). Prevents brittle tests. Read this skill first, then write tests.

Testing & QA

Testing Skills with Subagents

8

Freddy-CHEN-ux/00_claude_skills

Use to validate process documentation. Apply TDD to skill writing: RED (run without skill, document failures) → GREEN (write skill) → REFACTOR (close loopholes). Test under pressure: time constraints, sunk cost, exhaustion, authority.

Testing & QA

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.