smithery.ai

auto-testing

Automatically generate and run tests after each code change. Use when: any code is generated or modified in the pipeline.

First seen Mar 25, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,594 B
  • docs SUMMARY.md 172 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Auto Testing

Run tests automatically. User sees only pass/fail.

When to Run

After every:

  • Component generation
  • Feature addition
  • Code modification
  • Refactoring

Test Generation

For each code change, generate:

Code Type Test Type
Component Render, interaction
API endpoint Request/response
Utility function Unit tests
Form Validation, submission
Auth flow Login, logout, protected

Test Patterns

Components

test('renders correctly', () => {
  render(<Component />);
  expect(screen.getByRole('button')).toBeInTheDocument();
});

test('handles click', async () => {
  const onClick = jest.fn();
  render(<Component onClick={onClick} />);
  await userEvent.click(screen.getByRole('button'));
  expect(onClick).toHaveBeenCalled();
});

API

test('returns data', async () => {
  const response = await fetch('/api/items');
  expect(response.status).toBe(200);
  const data = await response.json();
  expect(data.items).toBeDefined();
});

Reporting

Status User Sees
All pass ✅ (nothing else)
Some fail "Fixing issues..." then ✅
Can't fix ❌ + simple explanation

Hidden Details

User never sees:

  • Test file contents
  • Number of tests
  • Coverage percentage
  • Individual test names

Only: ✅ works or ❌ problem