pytest-workflow
Pytest Workflow
Overview
Use this skill to design pytest suites that are fast enough for daily feedback and stable enough for CI gates.
Scope Boundaries
- Use this skill when the task matches the trigger condition described in
description. - Do not use this skill when the primary task falls outside this skill's domain.
Shared References
- Trigger examples:
references/trigger-and-examples.md
- Fixture boundary rules:
references/fixture-boundary-rules.md
- Determinism rules:
references/pytest-determinism-rules.md
Templates And Assets
- Test plan template:
assets/pytest-test-plan-template.md
- Fixture stability checklist:
assets/pytest-fixture-stability-checklist.md
- Command profile template:
assets/pytest-command-profile-template.md
Inputs To Gather
- Python modules and behaviors at risk.
- Fixture graph, dependency seams, and isolation constraints.
- Marker strategy and CI runtime/cost limits.
- Known flaky paths (async timing, shared state, environment coupling).
Deliverables
- Pytest test strategy and case matrix.
- Fixture and parametrization policy.
- Local-fast and CI-full command profiles.
- Residual risk and follow-up actions.
Workflow
- Build case strategy with
assets/pytest-test-plan-template.md. - Apply fixture rules from
references/fixture-boundary-rules.md. - Validate determinism using
references/pytest-determinism-rules.md. - Define execution profiles in
assets/pytest-command-profile-template.md. - Finalize with
assets/pytest-fixture-stability-checklist.md.
Quality Standard
- Fixtures are explicit, scoped, and deterministic.
- Case coverage includes happy/edge/failure paths.
- Command profiles are reproducible across local and CI.
Failure Conditions
- Stop when fixture design causes hidden shared state behavior.
- Stop when test determinism cannot be achieved for critical flows.
- Escalate when runtime cost blocks practical feedback loops.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9