jest-testing-workflow
Jest Testing Workflow
Overview
Use this skill to design and run Jest suites that are stable, meaningful, and decision-ready for merge 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 and expected deliverables:
references/trigger-and-examples.md
- Mock boundary decision rules:
references/mock-boundary-decision-rules.md
- Determinism rules:
references/jest-determinism-rules.md
Templates And Assets
- Test plan template:
assets/jest-test-plan-template.md
- Command profile template:
assets/jest-command-profile-template.md
- Flake triage checklist:
assets/jest-flake-triage-checklist.md
Inputs To Gather
- Change scope and affected JS/TS modules.
- Runtime assumptions (
node/jsdom) and mock boundaries. - CI constraints for runtime and coverage gates.
- Known flaky areas (async timers, shared state, external dependencies).
Deliverables
- Jest test strategy with mock/timer/environment policy.
- Assertion matrix for happy, edge, and failure paths.
- Local-fast and CI-full command profiles.
- Residual flakiness risk log with owner and next action.
Workflow
- Clarify decision question and mandatory quality constraints.
- Draft strategy using
assets/jest-test-plan-template.md. - Decide mock boundaries with
references/mock-boundary-decision-rules.md. - Define execution profiles in
assets/jest-command-profile-template.md. - Stabilize async/timer behavior with
references/jest-determinism-rules.md. - Run checks and close with
assets/jest-flake-triage-checklist.md.
Quality Standard
- Trigger fit and test depth are explicit.
- Mock strategy preserves behavior confidence for critical paths.
- Async/timer behavior is deterministic in local and CI runs.
- Evidence is reproducible with exact commands and artifacts.
Failure Conditions
- Stop when mock strategy hides behavior that must be integration-visible.
- Stop when command profile is not reproducible across local/CI.
- Escalate when flakiness persists after deterministic controls.
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