Skip to content
cccskills
FreePublished on GitHub

test-software

Design, implement, and evaluate risk-based software tests across unit, integration, contract, end-to-end, and regression layers. Use when adding tests, reproducing bugs, improving coverage, diagnosing flaky tests, or defining a test strategy; do not use to change production behavior unless the user also requests implementation.

The English summary is being prepared. Showing the original description.

See how to install

Files included (3)

  • SKILL.md2.0 KB
  • agents/openai.yaml224 B
  • references/test-strategy.md2.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Test Software

Test contract

  • Define the behavior, invariant, or defect before selecting a test layer.
  • Use the lowest layer that observes the risk without hiding the integration boundary under test.
  • Test behavior rather than private implementation details.
  • Avoid snapshots that hide meaningful assertions.
  • Do not mock the component whose integration contract is under test.
  • Control time, randomness, concurrency, and external dependencies explicitly.
  • Keep fixtures minimal and readable.
  • Do not “fix” flaky tests by adding blind retries or sleeps.
  • Do not claim a regression test without proving it fails against the broken behavior when feasible.
  • Treat tests as potentially state-changing: they may write databases, queues, files, snapshots, browsers, or external sandboxes.
  • Do not run tests against production, shared customer data, or external services without explicit authorization and a verified isolation strategy.
  • Stop when the configured test target or cleanup behavior is ambiguous.

Execute and report

Read references/test-strategy.md when choosing test layers or specialized methods, investigating flakes, or planning cross-service coverage.

Build deterministic fixtures, implement the smallest high-value set, and run focused tests repeatedly before broader required checks. Separate product, test, and environment failures.

For a strategy request, return:

  1. risks in priority order;
  2. proposed test layer for each risk;
  3. fixtures and dependencies;
  4. commands to run;
  5. coverage intentionally deferred.

For implementation, report focused and broader checks separately.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Build or modify backend APIs, services, jobs, persistence, and integrations while preserving contracts, authorization, data integrity, and failure behavior. Use for server-side features, database changes, background processing, backend defects, and service refactors; do not use for frontend-only or infrastructure-only work.

The English summary is being prepared. Showing the original description.

Phelan164/codex-howto14Updated Oct 17, 2026

Build or modify frontend interfaces using repository-native components while preserving accessibility, responsive behavior, state handling, and visual verification. Use for UI features, design implementation, forms, client-side defects, and frontend refactors; do not use for backend-only or infrastructure-only work.

The English summary is being prepared. Showing the original description.

Phelan164/codex-howto14Updated Oct 17, 2026

Select the smallest useful Codex engineering workflow from this repository's existing skills. Use when a task spans multiple engineering concerns, the user is unsure which skill to invoke, or loading every specialist would waste context; return a recommendation only and do not execute the engineering task.

The English summary is being prepared. Showing the original description.

Phelan164/codex-howto14Updated Oct 17, 2026

Implement a repository code or configuration change through reproduction, focused checks, review, and evidence. Use for end-to-end features and fixes; not for explanation-only, review-only, research, content publishing, or production operations.

The English summary is being prepared. Showing the original description.

Phelan164/codex-howto14Updated Oct 17, 2026

Review a small code or documentation change and return only evidence-backed correctness findings. Use in the Codex How To local plugin lab; do not modify files or post remote comments.

The English summary is being prepared. Showing the original description.

Phelan164/codex-howto14Updated Oct 17, 2026

Maintain a review-first Markdown knowledge base for Codex practices with source provenance, engineering capture, citation-aware queries, explicit archive and promotion, and deterministic linting. Use when asked to capture a durable engineering lesson, ingest Codex research, query or archive what the repository knows, check wiki health, reconcile conflicting guidance, or promote verified knowledge.

The English summary is being prepared. Showing the original description.

Phelan164/codex-howto14Updated Oct 17, 2026

See all skills by Phelan164

Report a problem with this skill