跳到正文
cccskills
免费在 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.

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(3)

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

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

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.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

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.

中文简介正在准备中。当前显示原文说明。

Phelan164/codex-howto142026年10月17日 更新

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.

中文简介正在准备中。当前显示原文说明。

Phelan164/codex-howto142026年10月17日 更新

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.

中文简介正在准备中。当前显示原文说明。

Phelan164/codex-howto142026年10月17日 更新

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.

中文简介正在准备中。当前显示原文说明。

Phelan164/codex-howto142026年10月17日 更新

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.

中文简介正在准备中。当前显示原文说明。

Phelan164/codex-howto142026年10月17日 更新

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.

中文简介正在准备中。当前显示原文说明。

Phelan164/codex-howto142026年10月17日 更新

查看 Phelan164 的全部技能

报告此技能的问题