neonwatty/linkparty · Archived

gen-test

Generate Vitest tests for a file following project conventions. Use when asked to create tests for a source file.

First seen Apr 7, 2026

Installation

$ npx skills add neonwatty/linkparty --skill gen-test

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

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 neonwatty/linkparty.

npx skills add neonwatty/linkparty

Browse all from neonwatty/linkparty

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

Also listed on

Alternate registries and mirrors of this skill.

Repository health

Default branch main
Open issues 1
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,399 B
  • docs SUMMARY.md 129 B

History

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

SKILL.md

Generate tests for: $ARGUMENTS

Test Stack

  • Runner: Vitest (vitest run)
  • React: @testing-library/react with @testing-library/user-event
  • Assertions: @testing-library/jest-dom for DOM matchers, Vitest expect for everything else
  • Mocking: vi.mock() for modules, vi.fn() for functions

Conventions

  1. Read the existing test at app/api/queue/items/route.test.ts for the project's testing patterns
  2. Read the source file specified in $ARGUMENTS
  3. Place the test file adjacent to the source: <filename>.test.ts or <filename>.test.tsx
  4. Use describe blocks grouped by function/component, with it for individual cases
  5. Mock Supabase client when testing code that uses @supabase/supabase-js or @supabase/ssr
  6. Mock process.env in beforeEach, restore in afterEach
  7. For React components: test user interactions, rendered output, and edge cases
  8. For API routes: test request validation, success paths, and error handling
  9. For utility functions: test happy paths, edge cases, and error conditions

After Generation

Run the tests to verify they pass:

npx vitest run --reporter=verbose <test-file-path>

Fix any failures before finishing.