GQ

govardhanrekha/qa-skill.md-files

开发工具

本页由 AI 翻译,技术细节请以原文为准。 查看原文

24 stars 质量 51 趋势 18

为整个软件测试生命周期提供AI代理技能和工具:需求分析、测试规划、测试设计、执行、缺陷管理、关闭和测试自动化。

概览

为整个软件测试生命周期提供AI代理技能和工具:需求分析、测试规划、测试设计、执行、缺陷管理、关闭和测试自动化。 该仓库包含可复用、自包含的指令集,指导AI编码代理(Claude Code、GitHub Copilot、Cline等)执行专业的质量保证和测试任务。最初只是一个测试计划生成器,现在已经完整 │ ├── stlc_manual_testing/ # STLC 技能包 — 7 阶段,14 项技能 │ └──� 01_jira-需求分析// # 第一阶段 — 需求分析 │ ├── 02_testplan-创建器-通过jira_LIVE//# 第二阶段 — 测试规划(旗舰)│ │ ├── SKILL.md │ │ ├── 上下文/How_to_Create_TestPlan_VWO.md │ │ ├── 副驾驶/测试计划.prompt.md │ │ ├── 参考文献/需求清单.md │ │ ├── 脚本/fetch_jira.sh │ │ └── 模板/测试计划模板。

概述(AI 翻译)

为整个软件测试生命周期提供AI代理技能和工具:需求分析、测试规划、测试设计、执行、缺陷管理、关闭和测试自动化。

该仓库包含可复用的代理技能,自包含的指令集,指导AI编码代理(如Claude Code、GitHub Copilot、Cline等)执行专业的质量保证和测试任务。最初是一个测试计划生成器,现在已成为完整的STLC技能包

📦 仓库结构

│ ├── stlc_manual_testing/ # STLC技能包 — 7个阶段,14个技能 │ ├── 01_jira-需求分析器/ # 第一阶段 — 需求分析 │ ├── 02_testplan-creator-via-jira_LIVE/ # 第二阶段 — 测试计划(旗舰) │ │ ├── SKILL.md │ │ ├── context/How_to_Create_TestPlan_VWO.md │ │ ├── 副驾驶/测试计划.prompt.md │ │ ├── 参考文献/需求检查表.md │ │ ├── 剧本/fetch_jira.sh │ │ └── template/test-plan-template.md │ ├── 03-test-design/ │ │ ├── 测试-场景-设计师/ │ │ └── API-test-designer/ │ ├── 04-测试案例开发/ │ │ ├── 测试案例作者/ │ │ └── 测试-数据生成器/ │ ├── 05-测试-执行/ │ │ ├── 自动化-脚本生成器/ │ │ ├── 回归组选择器/

本页由 AI 翻译,技术细节请以原文为准。

README

以下为原文 README 节选,完整内容请查看原文。

AgentSkills

AI agent skills and tools for the full software testing lifecycle: requirement analysis, test planning, test design, execution, defect management, closure, and test automation.

This repository contains reusable agent skills, self-contained instruction sets that guide AI coding agents (Claude Code, GitHub Copilot, Cline, etc.) to perform specialized QA and testing tasks. What started as a single Test Plan Generator is now a full STLC skill pack

📦 Repository Structure

│ ├── stlc_manual_testing/ # STLC skill pack — 7 phases, 14 skills │ ├── 01_jira-requirement-analyzer/ # Phase 1 — Requirement Analysis │ ├── 02_testplan-creater-via-jira_LIVE/ # Phase 2 — Test Planning (flagship) │ │ ├── SKILL.md │ │ ├── context/How_to_Create_TestPlan_VWO.md │ │ ├── copilot/test-plan.prompt.md │ │ ├── references/requirement-checklist.md │ │ ├── scripts/fetch_jira.sh │ │ └── template/test-plan-template.md │ ├── 03-test-design/ │ │ ├── test-scenario-designer/ │ │ └── api-test-designer/ │ ├── 04-test-case-development/ │ │ ├── test-case-writer/ │ │ └── test-data-generator/ │ ├── 05-test-execution/ │ │ ├── automation-script-generator/ │ │ ├── regression-suite-selector/ │ │ └── test-execution-tracker/ │ ├── 06-defect-management/ │ │ ├── bug-reporter/ │ │ ├── bug-triage-assistant/ │ │ └── rca-analyzer/ │ └── 07-test-closure/ │ ├── test-coverage-analyzer/ │ └── test-closure-reporter/


---

## 🗺️ STLC Roadmap — which skill fires when

```mermaid
flowchart LR
    A["01 RequirementAnalysis"] --> B["02 TestPlanning"]
    B --> C["03 TestDesign"]
    C --> D["04 Test CaseDevelopment"]
    D --> E["05 TestExecution"]
    E --> F["06 DefectManagement"]
    F --> G["07 TestClosure"]

    A -.- A1[jira-requirement-analyzer]
    B -.- B1[test-plan-generator]
    C -.- C1[test-scenario-designerapi-test-designer]
    D -.- D1[test-case-writertest-data-generator]
    E -.- E1[automation-script-generatorregression-suite-selectortest-execution-tracker]
    F -.- F1[bug-reporterbug-triage-assistantrca-analyzer]
    G -.- G1[test-coverage-analyzertest-closure-reporter]

🧰 STLC Manual Testing Pack

Concept: One skill per STLC activity. Each skill is a SKILL.md with a routing description, a step-by-step workflow, an output contract, and guardrails, so any agent produces the same shape of artifact every time.

Why: QA work done ad-hoc by an agent drifts: fabricated acceptance criteria, unprioritized scenarios, bug reports missing repro steps. Encoding each activity as a skill makes the output repeatable and reviewable.

Q&A — why a skill pack instead of one mega-prompt?

在 GitHub 查看完整 README

推荐工具

换一个关键词,或者移除筛选条件。

安装

npx skillfish add govardhanrekha/qa-skill.md-files
新手?先看 mcpskill.org 教程 →