メニュー
Test quality assessment criteria for reviewing tests. Apply when evaluating tests for substantive coverage, organization, maintainability, and realistic test data variety.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Google-style docstring conventions for Python code. Apply when writing or reviewing functions, classes, or modules that need documentation.
Python naming conventions for this codebase. Apply when writing or reviewing Python code including functions, classes, variables, and constants.
Python type hint conventions for this codebase. Apply when writing or reviewing Python code that needs type annotations on functions, classes, or variables.
Essential Pythonic idioms and conventions. Apply when writing or reviewing Python code to ensure idiomatic patterns like comprehensions, built-in functions, context managers, and unpacking.
Python code organization conventions for this codebase. Apply when structuring modules, organizing imports, designing file layouts, or moving functions/classes within or between files. Use PROACTIVELY when users request to check code organization, move code, or clean up and reorganize a module.
Refactoring complex functions into smaller, pure helper functions. Apply when function complexity is exceeded or when extracting helper functions during refactoring. If tasked with fixing ruff lint errors related to complexity, ALWAYS trigger this skill.
| name | test-quality |
| description | Test quality assessment criteria for reviewing tests. Apply when evaluating tests for substantive coverage, organization, maintainability, and realistic test data variety. |
| user-invocable | false |
| layers | {"rules":"rules.md","examples":"examples.md"} |
Evaluate whether tests verify true functionality rather than rubber-stamping code with superficial assertions.
Layers:
rules.md - Quick reference and severity guidanceexamples.md - Detailed code examples| Factor | Question | Severity if problematic |
|---|---|---|
| Substantive assertions | Does the test prove anything meaningful? | Critical |
| True functionality | Is observable behavior tested, not implementation? | Critical |
| Test organization | Are tests in the right module and cohesive? | Improvement |
| Edge case coverage | Are error paths and boundaries tested? | Critical/Improvement |
| Test data variety | Is data varied or repetitive? | Improvement |
| Fixture usage | Are fixtures reducing duplication without tight coupling? | Improvement |
| Mock discipline | Are mocks used only when necessary? | Improvement/Critical |
| Tests run | Do tests actually pass without errors? | Critical |
A test is valuable if:
For rules: see rules.md
For examples: see examples.md