Skip to content
cccskills
FreePublished on GitHub

test

Run the test suite and report results. Use after making changes to verify nothing is broken. Reads the test command from claude/build.md.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md1.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Test Skill

Run tests and report results with actionable failure analysis.

Protocol

1. Read the test command

Read claude/build.md for the test command and any special flags.

2. Run tests

# Use the command from claude/build.md
# Example: npm test 2>&1 | tail -50

For targeted tests (faster feedback):

# Example: npm test -- --testPathPattern=<filename> 2>&1 | tail -30

3. Analyze results

  • All pass: report summary and exit
  • Failures: analyze each failure

4. For each failing test

A. Read the exact assertion failure:

Expected: <value>
Received: <value>

B. Find the source of the failure:

  • What code is the test exercising?
  • What did the recent change touch?
  • Is this a pre-existing failure or newly introduced?

C. Fix or flag:

  • If newly introduced by current change: fix it
  • If pre-existing: document it, do NOT fix unrelated failures
  • If test itself is wrong: flag for user review (never silently delete a failing test)

5. Re-run after fixes

Keep running until all tests pass (or all failures are documented as pre-existing).

6. Report

Tests: PASS — 142 passed, 0 failed, 0 skipped

or

Tests: FAIL — 140 passed, 2 failed, 0 skipped
Newly introduced failures:
  - test/auth.test.ts:45 — [failure reason + fix applied]
Pre-existing failures (not caused by current change):
  - test/legacy.test.ts:12 — [noted, not fixed]

Rules

  • NEVER delete a failing test to make the suite pass
  • NEVER mock the thing being tested
  • NEVER mark a task complete with failing tests
  • Pre-existing failures must be distinguished from introduced failures

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

ask

Free

Route a codebase question to the right tool — structural graph, semantic search, or risk analysis. Use when you need to find or understand code without knowing exact file names.

The English summary is being prepared. Showing the original description.

brain-bootstrap/claude-code-brain-bootstrap11Updated Apr 25, 2026

Auto-configure CLAUDE.md and claude/ knowledge docs for a new project. Use when setting up Brain Bootstrap in a new repository. Discovers the codebase, fills in templates, and writes project-specific configuration.

The English summary is being prepared. Showing the original description.

brain-bootstrap/claude-code-brain-bootstrap11Updated Apr 25, 2026

Use before any new feature, component, or behavioral change — when you need to explore requirements and design before writing code

The English summary is being prepared. Showing the original description.

brain-bootstrap/claude-code-brain-bootstrap11Updated Apr 25, 2026

Activate safety guards for the session. Use /careful before critical operations — blocks rm -rf, DROP TABLE, git push --force, kubectl delete namespace, docker system prune via PreToolUse hook.

The English summary is being prepared. Showing the original description.

brain-bootstrap/claude-code-brain-bootstrap11Updated Apr 25, 2026

Generate a user-facing changelog from git commits — categorize, filter noise, translate to user language. Runs in isolated fork context.

The English summary is being prepared. Showing the original description.

brain-bootstrap/claude-code-brain-bootstrap11Updated Apr 25, 2026

Save session state before context gets full or before ending. Writes current task state, branch, and loaded docs to claude/tasks/todo.md so the next session can resume cleanly.

The English summary is being prepared. Showing the original description.

brain-bootstrap/claude-code-brain-bootstrap11Updated Apr 25, 2026

See all skills by brain-bootstrap

Report a problem with this skill