메뉴
Run Houndarr tests with various options (full suite, single file, keyword filter, coverage). Use when the user asks to run tests, run pytest, check test status, or invokes /test. Trigger phrases include run tests, test, pytest, coverage.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Houndarr's source layout and architectural patterns at file granularity. Loads when reading or editing src/houndarr/. Covers the per-file purpose for auth/, clients/, engine/, routes/, services/; the wire-models vs domain-models split; the *arr API spec snapshots under docs/api/; and pointers to the more specific database / engine skills for narrower scopes.
Houndarr's SQLite schema and migration discipline. Loads when reading or editing src/houndarr/database.py. Covers the schema table reference, the SCHEMA_VERSION bump checklist, and the version-locking rule for migration constants that prevents later renames from retroactively breaking earlier rebuild migrations.
Houndarr's CHANGELOG.md style guide and entry rules. Loads when reading or editing CHANGELOG.md or VERSION. Covers the noun-led present-tense voice, the 80-160 character length target, vocabulary the operator can act on, banned phrasings, what does not belong in a changelog, separator rules, and the bullet-justification protocol that prevents drafting from PR titles or memory.
Houndarr's CI workflow reference and branch protection. Loads when reading or editing .github/workflows/. Covers the 11 required status checks (exact names matter for branch protection), the additional non-required workflows, the paths-ignore + ci-skip pattern that keeps docs-only PRs green, and the rule against changing required check job names.
Houndarr-specific Python conventions on top of the global python skill. Loads when reading or editing .py files in this repo. Covers the noqa/nosec suppression table, the AppSettings-as-plain-dataclass decision, the frozen-dataclass-with-slots invariant for domain models, the per-module logger pattern, and the background-task error-handling shape.
Houndarr's pytest patterns. Loads when reading or editing tests/ files. Covers the fixture dependency graph, the FK seeding pattern for cooldowns/search_log tests, the local _login() and CSRF helpers in route tests, and the auth-state reset in test_settings.
| name | test |
| description | Run Houndarr tests with various options (full suite, single file, keyword filter, coverage). Use when the user asks to run tests, run pytest, check test status, or invokes /test. Trigger phrases include run tests, test, pytest, coverage. |
Parse the user's argument and run the appropriate test command. Argument forms: [full|file:<path>|keyword:<expr>|coverage] or a bare path.
full: run the full test suite..venv/bin/pytest
file:<path>: run a single test file with verbose output..venv/bin/pytest <path> -v
keyword:<expr>: run tests matching a keyword expression..venv/bin/pytest -k "<expr>" -v
coverage: run with coverage reporting..venv/bin/pytest --cov=houndarr --cov-report=term-missing
.venv/bin/pytest <path> -v
Report pass/fail clearly. If there are failures, show the failing test names and short tracebacks. Do not recite pass counts unless there are failures to contextualize.