Skip to content

avibebuilder/claude-prime / .claude/skills/test

Use when the user wants to know if something works — the answer requires running code, not analyzing it. Output is a verdict backed by evidence: passed, failed, or broken. Primary triggers: 'run the tests', 'does X still work after my change?', 'did the merge break anything?', 'verify the fix worked', 'check if the endpoint returns X', 'confirm nothing regressed', 'run tests/unit/test_foo.py', 'let me know the results', 'make sure my changes didn't break anything'. Hard stops — do NOT use for: reviewing test code for quality/coverage gaps, debugging why test infrastructure/databases/seed scripts are misbehaving, writing or fixing tests, diagnosing root causes of unexpected behavior. The deciding question: is the user asking for the result of executing something, or asking for help understanding/analyzing/improving something? If it's the latter, use diagnose or review-code instead.

FileKindSize
SKILL.mdskill md6.7 KB
references/backend-verification.mdmarkdown2.8 KB
references/frontend-verification.mdmarkdown3.8 KB
references/regression-strategy.mdmarkdown3.4 KB
teammate.mdmarkdown3.3 KB

references/backend-verification.md

View on GitHub
# Backend Verification

Patterns for verifying backend changes: APIs, database operations, services, background jobs, and data pipelines.

## API Endpoint Verification

### Direct Request Testing

The most reliable way to verify an API change is to call it.

**What to check on each response:**
- Status code matches expectation (not just "is 200" — a 201 for creation, 204 for deletion, etc.)
- Response body structure and key fields
- Error responses for invalid inputs (400, 422)
- Auth enforcement (401/403 for missing/wrong credentials)
- Edge cases: empty payloads, missing required fields, boundary values

**Example verification sequence for a new endpoint:**
```bash
# Happy path
curl -s -w "\n%{http_code}" -X POST http://localhost:3000/api/items \
  -H "Content-Type: application/json" \
  -d '{"name": "test", "price": 10.99}'

# Missing required field
curl -s -w "\n%{http_code}" -X POST http://localhost:3000/api/items \
  -H "Content-Type: application/json" \
  -d '{"name": "test"}'

# Auth check (if applicable)
curl -s -w "\n%{http_code}" -X POST http://localhost:3000/api/items
```

### Integration Test Patterns

When the project has integration tests (tests that hit a real or test database):
- Run only the relevant test file/suite, not the entire integration suite
- Check that test fixtures match the scenario you're verifying
- Watch for tests that pass because they test old behavior — a renamed field that the test hasn't caught yet

### Database Verification

For changes that modify database state:
- Verify the actual data after an operation — don't trust the API response alone if the claim is about persistence
- For schema changes, confirm both the forward migration and that existing data survives the migration

### Background Jobs / Queue Workers

Harder to verify because effects are asynchronous:
- Check the job was enqueued (inspect the queue)
- If possible, trigger the job synchronously in test mode
- Verify the side effect (email sent, file created, record updated) rather than just the enqueue

## Service-to-Service Verification

When the change involves communication between services:
- Verify the contract (request/response schema) matches what the consuming service expects
- If mocks exist, check they're up to date with the real interface
- For message-based communication (events, pub/sub), verify the message format and that consumers handle it

## What Makes Backend Evidence Strong

| Strong evidence | Weak evidence |
|----------------|---------------|
| Actual HTTP response with correct status + body | "The code looks right" |
| Database query showing correct state after operation | "The migration file is correct" |
| Test output showing the specific case passes | "All tests pass" (but none cover this) |
| Error response for invalid input | Only tested the happy path |
| Verified under auth constraints | Tested without auth |
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall