66 tagged pytest, measured the same way as everything else here.
Browse within: python 58project-template 27python-project-template 27python3 27uv 27pylint 21fastapi 5
Skill Claude CodeCodex
Use when running, writing, or debugging tests in the GAC project. Covers test structure, pytest commands, provider testing patterns, and integration vs unit test practices.
rollinsio/beyond-test-coverage
Skill Claude CodeCodex
Turn a test-quality scorecard JSON into a self-contained interactive HTML readout — hero stats, a per-axis Win/Tie/Loss distribution chart, and the full per-suite matrix. Use when the user wants to visualize benchmark/scorecard results, regenerate the results dashboards in docs/, or render a {baselines, arms}…
rollinsio/beyond-test-coverage
Skill Claude CodeCodex
Audit, harden, or generate unit tests with a focus on mutation-resistance and durable quality — not just coverage %. Use when the user asks to improve or harden test quality, make tests less fragile/brittle, review tests for anti-patterns (error-message-substring asserts, private-symbol access, tautological…
MarcusJellinghaus/mcp-tools-py
Skill Claude CodeCodex
Autonomous issue analysis — supervisor delegates to engineer subagents.
MarcusJellinghaus/mcp-tools-py
Skill Claude CodeCodex
Approve issue to transition to next workflow status.
MarcusJellinghaus/mcp-tools-py
Skill Claude CodeCodex
Update GitHub issue with refined content from analysis discussion.
Skill Claude CodeCodex
Author test stub files (.pyi) whose signatures express the domain, relationships, and compositions, as the first contract surface.
Skill Claude CodeCodex
Author the persistence schema as a binding contract from the captured external shapes and the interview — before any test stub is written.
Skill Claude CodeCodex
Compile the contract set in your head — simulate how the real application would run from the specs, and disprove (or confirm) it works before any source .py is written.
Skill Claude CodeCodex
This skill should be used when creating a service class, adding an API route, defining Pydantic schemas, writing error handling, reviewing code style, checking project directory structure, writing or running database migrations, or deciding what belongs in which layer. Covers style, naming, error handling, logging…
Skill Claude CodeCodex
This skill should be used when writing unit tests, integration tests, creating test factories, mocking dependencies, or reviewing test coverage. Covers test pyramid, conventions, factories, and per-layer rules.
Skill Claude CodeCodex
Design or review a modular monolith by defining bounded contexts, assigning ownership, enforcing public service-layer interfaces, keeping dependencies one-way, and separating shared technical code from business code. Use when planning modules, adding a feature that crosses module boundaries, or finding direct…
Skill Claude CodeCodex
Skill "docs" from SpecLeft/specleft, covering specleft cli reference, setup, workflow, quick checks and safety.
Skill Claude CodeCodex
Pytest fixtures, parametrize, mock/monkeypatch, async testing with pytest-asyncio, and coverage reporting.
Skill Claude CodeCodex
Before finalizing structured or extracted output in a domain with declared safety invariants, verify the output against your invariant suite and refuse to ship when a locked field was model-auto-filled. Invoke when the user or task involves high-stakes structured extraction, compliance fields, or pass/fail results…