Specx Tests
Add or refine tests for specx Python services. Use when creating unit tests for use cases/services, integration tests for FastAPI controllers or infrastructure adapters, e2e smoke tests, architecture import guardrails, DI override tests, pytest fixtures, or coverage and boundary checks.
Install
npx skills add maksimzayats/specx --skill specx-testsgit clone --depth 1 https://github.com/maksimzayats/specx.git /tmp/specx
mkdir -p ~/.claude/skills
cp -r /tmp/specx/.agents/skills/specx-tests ~/.claude/skills/specx-testsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# specx Tests Use this skill when behavior, wiring, or architecture boundaries need tests. Read `references/testing.md` before creating test files. ## Test Layers - `tests/_support/`: generic clients, DB helpers, and shared integration helpers only. This is not a test suite and does not hold project-specific doubles. - `tests/unit/`: core services, use cases, and capabilities resolved from a fresh application container returned by the project's `get_container()`. - `tests/integration/`: real internal graph tests. Core use-case integration tests call resolved use cases against the transactional DB; delivery integration tests exercise HTTP mapping; migrations prove Alembic behavior. - `tests/e2e/`: optional whole-app smoke flows. - `tests/guardrails/`: optional programmatic `specx.testing.architecture.assert_specx_architecture` wrappers for genuinely project-specific extra rules. Standard packaged rules run through `uv run specx check`. ## Rules - Test behavior and boundaries, not implementation ceremony. - Required generated coverage is currently scoped to core services, use cases, and capabilities. - Mirror source module paths directly with flat test files, for example `tests/unit/core/tasks/services/test_title_service.py`. - Do not create per-target test folders, `harness.py`, target factories, or target harnesses. - `tests/unit/conftest.py` owns the fresh real-app `Container` fixture for unit
Details
- Skill name
specx-tests- Repository
- maksimzayats/specx
- Path
.agents/skills/specx-tests/SKILL.md- License
- MIT
- Repo updated
- 8 August 2026
FAQ
What does the Specx Tests skill do?
Add or refine tests for specx Python services. Use when creating unit tests for use cases/services, integration tests for FastAPI controllers or infrastructure adapters, e2e smoke tests, architecture import guardrails, DI override tests, pytest fixtures, or coverage and boundary checks.
How do I install the Specx Tests skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add maksimzayats/specx --skill specx-tests. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Specx Tests popular?
It lives in maksimzayats/specx, which has 198 GitHub stars and 33 forks.
Related skills
Specx Add Core Service
198maksimzayats/specx
Add or refactor a specx core scope service. Use when implementing focused reusable business/application behavior under a core scope services package, extracting logic from a use case, injecting deterministic collaborators, accepting an active unit of work, choosing between Service and Capability, or keeping business decisions away from delivery and infrastructure.
Specx Add Core Use Case
198maksimzayats/specx
Add or refactor a specx core scope use case. Use when implementing an externally meaningful application action under a core scope use_cases package, adding same-file command/query inputs, result DTOs, coordinating services, opening a unit-of-work transaction, or moving behavior out of delivery or infrastructure into class-based application code.
Specx Add Delivery Controller
198maksimzayats/specx
Add delivery controllers for specx services, especially FastAPI HTTP routes. Use when creating top-level `delivery/` request/response schemas, one controller per scoped use-case set, route registration, FastAPI lifecycle managers, HTTP error translation, delivery-only auth/rate-limit/request services, or integration tests that exercise the delivery edge.
Hare Lang
293mohitmishra786/low-level-dev-skills
Hare language skill for simple systems programming. Use when building with hare build/test/run, Hare stdlib, C FFI with @extern, tagged union error handling, or comparing Hare vs C/Zig. Activates on queries about Hare language, hare build, @extern, tagged union, or Hare stdlib.
Specx Sqlalchemy Migrations
198maksimzayats/specx
Add or repair Alembic migrations for specx SQLAlchemy services. Use when adding SQLAlchemy models or repositories, replacing metadata.create_all schema bootstraps, creating async Alembic env.py, adding migration Makefile targets, generating initial revisions, or testing migration drift.
Honest Thinking Partner
171aiskilloftheweek/claude-ai-skill-of-the-week
Activates a brutally honest thinking partner mode that sharpens reasoning, surfaces blind spots, dismantles flawed logic, and forces concrete action planning. Use this skill every time the user wants honest feedback on a plan, decision, or idea — especially when they seem to be rationalizing, avoiding something, or stuck. Also trigger when the user says things like "be honest with me", "tell me what you really think", "am I thinking about this wrong", "what am I missing", "stress-test this", "play devil's advocate", "challenge my thinking", "I need brutal feedback", or pastes a plan, decision,
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.