test-writer

How to write pytest tests for modules in this workspace. Load whenever you are about to write or extend tests.

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.

npx skills add https://github.com/genkit-ai/genkit --skill test-writer

명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.

로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md

소스 지침 · 읽기 전용 미리보기

name	test-writer
description	How to write pytest tests for modules in this workspace. Load whenever you are about to write or extend tests.

When writing pytest tests in this workspace:

One test file per module. foo.py lives next to foo_test.py (suffix, not prefix).
Cover the happy path AND at least one edge case. Empty input, duplicates, boundary values — pick what matters for the unit under test.
Use pytest.mark.parametrize when the same assertion runs over a small table of inputs. Keep IDs descriptive.
Name tests test_<unit>_<scenario>_<expected>. Examples: test_total_empty_cart_returns_zero, test_add_duplicate_item_merges_quantities.
Arrange / Act / Assert. Three clear blocks. No setup hidden in fixtures unless it's reused across at least two tests.
Assert behavior, not implementation. Don't reach into private attributes or count function calls; check the observable result.
Imports at module top. Don't import inside test functions.

TypeScript coding conventions, best practices, and patterns for writing clean, maintainable code.

Conventions for clean, idiomatic Python. Load whenever you read, edit, or write Python source files.

Explain concepts in very simple terms suitable for a five-year-old.

name	test-writer
description	How to write pytest tests for modules in this workspace. Load whenever you are about to write or extend tests.

When writing pytest tests in this workspace:

One test file per module. foo.py lives next to foo_test.py (suffix, not prefix).
Cover the happy path AND at least one edge case. Empty input, duplicates, boundary values — pick what matters for the unit under test.
Use pytest.mark.parametrize when the same assertion runs over a small table of inputs. Keep IDs descriptive.
Name tests test_<unit>_<scenario>_<expected>. Examples: test_total_empty_cart_returns_zero, test_add_duplicate_item_merges_quantities.
Arrange / Act / Assert. Three clear blocks. No setup hidden in fixtures unless it's reused across at least two tests.
Assert behavior, not implementation. Don't reach into private attributes or count function calls; check the observable result.
Imports at module top. Don't import inside test functions.