All categories
Testing & QA
Unit tests, integration tests, E2E, QA, validation, and test automation
- 31,122
- 1,297
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse testing & qa skills
Showing 3,601–3,624 of 31,122 skills
- Plans> **Status:** revised after one independent cross-model review (2026-08-24). > All seven findings were verified against the repository and accepted; the > adjudication log at the end records each disposition. Self-contained; a > reader needs no prior conversation context. **Goal:** Add a paired Claude/Codex skill, `cross-review-plan`, that lets the *current* agent session hand a plan to a fresh session of the *other* CLI (Claude ↔ Codex) for one independent review pass, monitor that session, ...Votes: 0GitHub stars: 12
- VerifyRun an explicit user-requested criteria-driven verification loop. Use when the user asks to define success criteria, close the loop against criteria, or rigorously verify non-code outputs. Do not use for a plain live-software check owned by end-to-end, routine coding completion, or narrower audit/debug checks.Votes: 0GitHub stars: 12
- Test SuiteCreate or expand high-value test suites for a codebase or specific module. Use when new tests, regression tests, coverage improvements, or test infrastructure are the deliverable; not for merely running an existing suite, reviewing code, or ordinary bug-fixing without a requested test deliverable.Votes: 0GitHub stars: 12
- Record DecisionsExtract and record architectural, algorithmic, or design decisions from the current session. Use for an explicit ADR/decision request, authorized end-of-session bookkeeping, or a significant chosen trade-off within an implementation task; not for unchosen proposals or read-only reviews.Votes: 0GitHub stars: 12
- Pin Elisp PrPin an Emacs/Elpaca package in dotfiles to a user-requested fork, branch or PR. Preserve one effective installation owner per active profile, existing recipe settings and configuration behavior. Not for merely reviewing a PR or auditing this skill.Votes: 0GitHub stars: 12
- End To EndUse when the agent must execute or directly observe decisive live software acceptance through a real user-visible or runtime surface, including browser, Emacs, terminal display, async/network delivery, persistence, or scheduler behavior. Automation may drive the actual surface. Do not use solely to give manual test instructions; explain, write, or review; run an automated E2E suite; deploy or check deployment health/status; reproduce research results; or verify pure logic.Votes: 0GitHub stars: 12
- DiagnoseEstablish the cause of unintended behavior in the user's agents, tools, or configuration before proposing or applying any remedy. Use whenever such behavior is reported or observed and its cause is not yet established. Not for ordinary code bugs, broad configuration audits, or repository-wide AI developer-experience reviews.Votes: 0GitHub stars: 12
- VerifyRun an explicit user-requested criteria-driven verification loop. Use when the user asks to define success criteria, close the loop against criteria, or rigorously verify non-code outputs. Do not use for a plain live-software check owned by end-to-end, routine coding completion, or narrower audit/debug checks.Votes: 0GitHub stars: 12
- Test SuiteCreate or expand high-value test suites for a codebase or specific module. Use when new tests, regression tests, coverage improvements, or test infrastructure are the deliverable; not for merely running an existing suite, reviewing code, or ordinary bug-fixing without a requested test deliverable.Votes: 0GitHub stars: 12
- Record DecisionsExtract and record architectural, algorithmic, or design decisions from the current session. Use for an explicit ADR/decision request, authorized end-of-session bookkeeping, or a significant chosen trade-off within an implementation task; not for unchosen proposals or read-only reviews.Votes: 0GitHub stars: 12
- Pr AuditAudit a specified PR or PR-ready branch for submission or post-revision readiness. Bind the exact base/head, review commits and net changes, run safe project checks and inspect applicable CI. An audit alone does not authorize fixes, history changes or publication.Votes: 0GitHub stars: 12
- Pin Elisp PrPin an Emacs/Elpaca package in dotfiles to a user-requested fork, branch or PR. Preserve one effective installation owner per active profile, existing recipe settings and configuration behavior. Not for merely reviewing a PR or auditing this skill.Votes: 0GitHub stars: 12
- End To EndUse when the agent must execute or directly observe decisive live software acceptance through a real user-visible or runtime surface, including browser, Emacs, terminal display, async/network delivery, persistence, or scheduler behavior. Automation may drive the actual surface. Do not use solely to give manual test instructions; explain, write, or review; run an automated E2E suite; deploy or check deployment health/status; reproduce research results; or verify pure logic.Votes: 0GitHub stars: 12
- DiagnoseEstablish the cause of unintended behavior in the user's agents, tools, or configuration before proposing or applying any remedy. Use whenever such behavior is reported or observed and its cause is not yet established. Not for ordinary code bugs, broad configuration audits, or repository-wide AI developer-experience reviews.Votes: 0GitHub stars: 12
- Telemetry PipelineUse when working on the silken_net telemetry / Proof-of-Growth pipeline — the uplink→verification→minting flow (CoAP intake → UnpackTelemetryWorker / TelemetryUnpackerService → Wallet#credit! → optimistic mint = live PATH 2; IoTeX verify → Chainlink = PATH 1, latent / activation-gated — ARCH.53), the Sidekiq strict-priority queues, TelemetryLog (RANGE-partitioned, KENOSIS — the bounds check runs in the unpacker before create!, never in the model), and the dual-computation integrity (server Fl...Votes: 0GitHub stars: 23
- Ml EngineeringUse when working on the silken_net ML surface — the TinyML acoustic model + log-mel DSP front-end (firmware/common/logmel*, tools/ml/), model training / dataset / INT8 export, or golden-vector parity. ⛔ The backend Rumale stress-index ML was REMOVED 2026-09-05 (У-ВЕЙ) — the skill records where it went and why; do not hunt for it in the tree. Operational playbook for the tools/ml `silken_ml` package, the three-impl parity model, and the local-verify recipes; routes to the 03_03 canon, does not...Votes: 0GitHub stars: 23
- Workflow Feature Driven OptimizationUse when 实施已知 CPython/CinderX 性能优化,完成代码、功能测试和收益验证。Votes: 0GitHub stars: 2
- Validation StrategyUse when 为 CPython/CinderX 实验选择验证范围或成本预算,决定是否扩大测试。Votes: 0GitHub stars: 2
- Pyperformance Suite RunUse when 正式运行 pyperformance 子集或全量并生成 run.json;单 worker 调试用 pyperformance-worker-run。Votes: 0GitHub stars: 2
- Cpython Runtime Test RunUse when 运行或重跑 CinderX RuntimeTests 功能测试、test_cinderx/lib test 集成测试。Votes: 0GitHub stars: 2
- Cinderx Fast ValidationUse when CinderX release 构建或 gate 重复编译缓慢,需要用 ccache 复用构建。Votes: 0GitHub stars: 2
- Test ReviewTest quality checklist, security testing requirements, dynamic analysis, and test organization conventions for Java/Spring Boot applications. Load when conducting test reviews.Votes: 0GitHub stars: 15
- Test ReviewTest quality checklist, security testing requirements, dynamic analysis, and test organization conventions for Go applications. Load when conducting test reviews.Votes: 0GitHub stars: 15
- Test ReviewTest quality checklist, security-testing requirements, and dynamic-analysis expectations — language-agnostic, with per-section slots a stack fills in. Load when conducting test reviews.Votes: 0GitHub stars: 15