Unit Test
Use when the user directly requests efficiency-aware multi-angle unit tests or a test report after code changes. Triggers include "단위 테스트", "유닛테스트", "테스트 돌려", "다방면 테스트", "테스트 문서 정리", and the English equivalents "unit test", "run the tests", "multi-angle tests", "write up the test results", and "/unit-test". Codex or Claude runs tests locally without calling another LLM, avoids duplicate full-suite gates, and writes a focused report to the project's test directory. Not for E2E, external DB/network checks, runtime verification, or performance benchmarks.
Install
/plugin marketplace add moveju112/skill_verifyThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add moveju112/skill_verify --skill unit-testgit clone --depth 1 https://github.com/moveju112/skill_verify.git /tmp/skill_verify
mkdir -p ~/.claude/skills
cp -r /tmp/skill_verify/skills/unit-test ~/.claude/skills/unit-testPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# unit-test — multi-angle unit testing after code changes The active host designs, runs, and documents unit tests for freshly changed code. Use the runtime identity supplied by the current session; never infer it from skill paths. Host-local only: never call the counterpart, crosscheck scripts, or another LLM. Respond in the language the user writes in — Korean request, Korean output; English request, English output. The report follows that same language. This rule document stays English regardless. ## 0. Invocation — explicit requests only - Use this skill only when the user explicitly asks for unit testing or its report. - Ordinary code modification does not trigger this skill. Do not offer unit tests merely because code changed. - A direct request to run unit tests IS the approval for local unit testing; do not ask again. - Approval covers local unit testing only. Never access an external DB, network, service, or runtime from this skill. Route those checks to a separate verification step with its own explicit permission. ## 1. Scope — what to test - `git diff HEAD` (or the session's edit list) → enumerate changed functions/methods. - Classify each check as `UNIT`, `STATIC`, `BUILD`, `INTEGRATION`, `RUNTIME`, or `PERFORMANCE`. This skill executes only local `UNIT`, plus the smallest useful `STATIC` or `BUILD` gate. List the other classes as uncovered; do not run them here. - Prefer pure-logic units and isolated local fixtures first.
Details
- Skill name
unit-test- Repository
- moveju112/skill_verify
- Path
skills/unit-test/SKILL.md- License
- MIT
- Repo updated
- 5 October 2026
- Listed in
- karanb192/awesome-claude-skills
FAQ
What does the Unit Test skill do?
Use when the user directly requests efficiency-aware multi-angle unit tests or a test report after code changes. Triggers include "단위 테스트", "유닛테스트", "테스트 돌려", "다방면 테스트", "테스트 문서 정리", and the English equivalents "unit test", "run the tests", "multi-angle tests", "write up the test results", and "/unit-test". Codex or Claude runs tests locally without calling another LLM, avoids duplicate full-suite gates, and writes a focused report to the project's test directory. Not for E2E, external DB/network checks, runtime verification, or performance benchmarks.
How do I install the Unit Test skill?
Claude Code plugin: /plugin marketplace add moveju112/skill_verify. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Unit Test popular?
It lives in moveju112/skill_verify, which has 1 GitHub stars and 0 forks, and is included in 1 curated skill list.
Related skills
Crosscheck
1moveju112/skill_verify
Claude-hosted Claude↔Codex crosschecks of improvement ideas, plans, and completed changes. Automatically selects independent proposals, draft critique, or mutual review and allows candid rejection. Use for explicit requests such as "크로스체크", "코덱스랑 핑퐁", "둘이 의견 취합해", "cross-check with codex", or "/crosscheck". Discussing or editing this skill does not authorize another model call.
Verify
1moveju112/skill_verify
Evidence-based local verification and explicitly requested Claude↔Codex crosschecks of improvement ideas, plans, and changes. Automatically selects independent proposals, draft critique, or mutual review, with candid recommendations and minimal exchanges. Shared by Claude Code and Codex. Generic verification stays local; discussing this skill is not permission to call another model. Direct multi-angle unit-test requests use the unit-test skill.
Audit Feature Gates
5TalonT-Org/AutoSkillit
Audit feature flag isolation — traces import chains, runtime gates, tool/skill tag coverage, UI surfaces, and test markers to detect leakage and miswiring.
QA
5GAGAA-HUE/ASHUO-claude-skills
Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, file issues conversationally, or mentions "QA session".
Audit Tests
5TalonT-Org/AutoSkillit
Audit the test suite for useless tests, consolidation opportunities, over-mocking, weak assertions, placement/organization issues, xdist safety violations, test path filter integrity, and other test quality issues. Use when user says "audit tests", "audit test suite", "review tests", or "test quality check". Generates an improvement plan in temp/ with explanations for each proposed change.
Migrate to Shoehorn
5GAGAA-HUE/ASHUO-claude-skills
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.