メニュー
Autonomous test writing agent. Use when developer wants tests written for changed files. Analyzes git diff, identifies components needing tests, writes unit tests following project conventions with Vitest.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | test-writer |
| description | Autonomous test writing agent. Use when developer wants tests written for changed files. Analyzes git diff, identifies components needing tests, writes unit tests following project conventions with Vitest. |
| allowed-tools | Bash, Read, Write, Edit, Glob, Grep |
| model | sonnet |
Write tests for newly added or changed code autonomously.
| Argument | Description |
|---|---|
| (none) | Run git status, find changed files, write tests |
[file-path] | Write tests for a specific file |
"Write tests for my changes"
"Write tests for src/app.tsx"
Follow .claude/rules/testing.md for all testing conventions (imports, patterns, framework).
Follow .claude/rules/coding.md for code style (naming, TypeScript, functional patterns).
1. Identify files needing tests:
git status --porcelain
git diff --name-only main..HEAD
Skip files that don't need tests:
lynx.config.ts, tsconfig.json, biome.json)index.ts that only re-export)*.module.scss)*.png, *.jpg)2. Analyze each changed file:
3. Study existing test patterns:
src/app.test.tsx)4. Write tests following the rules in .claude/rules/testing.md
5. Run tests to verify they pass:
npx vitest run --reporter=verbose
If tests fail, analyze the error, fix, and re-run. Retry up to 3 times before reporting the failure.
6. Return summary of tests written
Return summary:
Feature implementation workflow. Use when developer wants to implement a feature or fix - creates branch, plans, implements, and validates.
Git commands for branching, committing, merging, rebasing, and squashing. Use when developer needs to create branches, commit changes, merge or rebase branches, or squash commits.
GitHub commands (issues, PRs, ship). Use when developer needs to create issues, create/update PRs, address review comments, or ship experimental changes.
Project management commands (init, skill-up, diagram)
DeepSource commands (review issues). Use when developer needs to review and fix static analysis issues.
Generate assets from source files (icons, etc.)