Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Development

unit-test-grill

Lists unit-test scenarios without writing tests.

siberiacancode · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add siberiacancode/agent-skills --skill unit-test-grill

About this skill


name: unit-test-grill description: Lists unit-test scenarios without writing tests.

Call the Skill tool with "testing-best-practices", then use its "unit-test-grill" rule.

Delegated implementation: testing-best-practices

Source: https://github.com/siberiacancode/agent-skills/tree/e9f64378d5280ca0f31b89cb2c047275cd9a6b88/skills/testing-best-practices


name: testing-best-practices description: "Support QA and testing work across formats: planning checks, writing test cases, reviewing coverage, designing automation, creating locators for integration tests, and keeping automated tests focused on observable product behavior."

Testing Best Practices

Practical QA guidance for turning product behavior, requirements, and code paths into useful checks. Use this skill for manual test cases, test plans, coverage reviews, automation scenarios, unit tests, locators for integration tests, /unit-test-grill, and /testcase-grill.

The central idea is not a specific framework. The central idea is testing discipline:

  • Start from the user-visible or public contract: what must work, what may fail, and what must never happen.
  • Choose the right testing format for the risk: exploratory notes, manual test cases, regression checklist, unit coverage, integration scenario, or automation task.
  • Make every check prove a meaningful behavior, requirement, branch, state transition, error path, or cleanup guarantee.
  • Keep coverage focused. Test independent dimensions separately, avoid noisy Cartesian products, and skip arbitrary edge values that only retest the platform.
  • Preserve project reality by reading nearby tests, existing QA artifacts, product flows, schemas, and automation conventions before adding new structure.
  • Treat integration-test locators and test data as maintained testing APIs, changing schema, implementation, and affected checks together.

Use the specific rule files after choosing the testing subject. The current detailed rules cover automated unit tests, semantic integration locators, and repository-stored product test cases; for other QA formats, apply the core defaults in this file and keep the output concrete enough for a tester or automation engineer to execute.

When to Apply

Reference these guidelines when:

  • Creating manual test cases, smoke checks, regression suites, acceptance scenarios, or exploratory charters.
  • Generating, revising, reviewing, or reorganizing structured test cases stored in the repository's test-case catalog.
  • Planning or reviewing automation coverage for application behavior.
  • Adding or reviewing automated tests for code.
  • Looking for missing behavioral coverage, branch coverage, state transitions, cleanup checks, or error paths.
  • Deciding how to name, order, and scope checks inside a test file or QA checklist.
  • Creating or reviewing a locator for integration tests, including the semantic name, schema path, JSX attribute, and affected checks.
  • Invoking /unit-test-grill to turn code behavior into a checklist without writing test code.
  • Invoking /testcase-grill to turn a page or block into a list of owned test cases without writing them into the catalog.

QA Defaults

  • Write each check around one behavior or requirement, with clear preconditions, action, and expected result when the format needs those fields.
  • Separate smoke, critical-path, regression, negative, boundary, permission, data-state, and recovery checks when that distinction changes execution priority.
  • Prefer scenario names that describe the promised behavior, not the implementation detail.
  • Include setup data, environment assumptions, and cleanup only when they affect reproducibility.
  • Mark automation candidates by stability and value: repeated critical paths, high-risk regressions, deterministic state, and reliable assertions come first.
  • Do not automate a scenario until its expected result, data requirements, and locator strategy are stable enough to maintain.
  • In reviews, report concrete missing checks or unstable assumptions; do not use coverage percentages or technology names as the main finding.

Rule Map

Read unit-test-conventions before any subject-specific unit-test rule.

  • unit-test-function - Public inputs, owned transformations, branches, errors, and async collaborator boundaries.
  • unit-test-react-hook - Public hook contract, changing arguments, async work, cleanup, and browser/listener behavior.
  • unit-test-ui-component-standalone - Independent component DOM, props, state, interactions, and accessibility.
  • unit-test-ui-component-compound - Public parts and the state, context, behavior, and accessibility relationships between them.
  • unit-test-grill - Scenario-planning mode for /unit-test-grill.

Read integration-test-locator-testids when adding or reviewing locators for application integration tests.

Read testcase-conventions before any subject-specific test-case rule.

  • testcase-file-structure - Folder and file ownership, coverage duplication, and where child screens and reusable blocks live.
  • testcase-naming - Dot-separated hierarchy, exact interface labels, and fixed forms for loading, empty-list, and data cases.
  • testcase-content - Atomic cases, user-oriented actions, concrete expected results, and the split between design, functional, and data checks.
  • testcase-preconditions - Case-file, folder, and global precondition scope.
  • testcase-grill - Case-planning mode for /testcase-grill.

How to Use

  1. Identify the testing goal: manual QA, test-case design, coverage review,
Read the complete source ↗