Qa Start
petrkindlmann/qa-skills/skills/qa-start作者 petrkindlmannb3bb61bd268bMIT168 个星标收录于 2026年10月9日更新于 2026年10月9日仓库4个月前更新
Sequenced launcher that bootstraps QA on a project with no QA in place. Chains qa-project-context → test-strategy → test-planning in one guided run, then points you at automation. Use when: "set up QA on a new project," "QA from scratch," "no QA exists yet," "/qa-start." Not for: onboarding a QA engineer to an existing team with existing tests — use qa-project-bootstrap. Not for: "which skill do I use" with no clear match — use qa-do. Related: qa-project-context, test-strategy, test-planning, qa-project-bootstrap, qa-do.
仅公开文件列表。将技能安装到工作区后即可查看文件内容。
| 路径 | 大小 | 类型 |
|---|---|---|
| SKILL.md | 7.1 KB | text/markdown |
更多来自 petrkindlmann/qa-skills 的技能
Visual Testing
petrkindlmann
指导使用 Playwright 截图以及 Chromatic、Percy、Argos CI 等托管工具进行视觉回归测试。
Unit Testing
petrkindlmann
指导使用 Jest、Vitest 和 pytest 编写有效的单元测试，涵盖测试替身、覆盖率门禁、快照、假定时器和变异测试。
Test Suite Curation
petrkindlmann
Audit a whole regression suite and prune/restructure it with evidence: per-test coverage fingerprinting, AST near-duplicate clustering, CI-history mining for never-failing and flaky tests, prune decision rules (redundant/obsolete/low-value/keep), smoke/core/extended tiering by risk and defect-detection history, and a defensible "what we deleted and why" record. Deletion is destructive — quarantine and human sign-off are mandatory. Use when: "audit the test suite," "prune redundant tests," "find duplicate tests," "which tests can we delete," "restructure into smoke/core/extended," "is this test pulling its weight," "shrink the regression suite." Not for: Judging whether an individual test is WELL-WRITTEN (smells, assertions) — that is ai-qa-review. Healing one flaky test at runtime — that is test-reliability. Bulk selector regeneration after a UI refactor — that is selector-drift-recovery. Related: ai-qa-review, coverage-analysis, test-reliability, risk-based-testing, qa-project-context.
Test Strategy
petrkindlmann
Produce a multi-quarter QA strategy document. Covers scope, risk-based prioritization, test levels (unit/integration/E2E), pyramid analysis, entry/exit criteria, quality KPIs, tool selection rationale, CI scaling levers, and timeline planning. Output is an actionable strategy document, not a shelf document. Use when: "test strategy," "QA strategy doc," "testing approach," "QA roadmap," "multi-quarter QA direction." Not for: a single-sprint or single-release plan — use test-planning. Not for: identifying which areas carry the most risk — use risk-based-testing first. Related: risk-based-testing, qa-metrics, release-readiness, test-planning, test-reliability.
Test Planning
petrkindlmann
为单个冲刺或发布制定一页式测试计划，涵盖覆盖映射、工作量估算、优先级排序、资源分配与排期。
Test Migration
petrkindlmann
指导测试套件在不同框架之间增量迁移，例如 Selenium、Cypress 或 Jest 迁移到 Playwright 或 Vitest，并支持并行 CI。
更多Software Development技能
Playground
anthropics
构建自包含的交互式 HTML 演练场，包含控件、实时预览和可复制的提示词输出。
M5 Onboard
anthropics
通过 USB 检测 M5Stack ESP32 开发板，刷写 UIFlow 2.0 固件并安装 MicroPython 应用包。
Cardputer Buddy
anthropics
指导迭代 Cardputer-Adv 的 MicroPython 应用包：添加应用、通过 USB 串口推送文件、查看日志并运行 REPL 命令。
Web Design Guidelines
vercel-labs
依据从远程来源获取的 Web Interface Guidelines 审查 UI 代码，并以 file:line 形式报告问题。
Vercel React Native Skills
vercel-labs
React Native 与 Expo 最佳实践规则，涵盖列表性能、动画、导航、UI 模式、状态与 monorepo 配置。
Vercel React Best Practices
vercel-labs
Vercel 的 React 与 Next.js 性能指南，以 70 条规则的形式用于编写、审查和重构代码。