qa-risk-analyzer skillA
qa-risk-analyzer is agent-read markdown (skill) from mingdui/ming-qa: 在测试用例设计之前，先识别高风险业务路径和必需的验证断言（oracle）。分析需求文档、代码 diff、已有用例和上下文， 找出资金/权限/状态机/并发/异步/数据一致性等高危区域，输出每条风险的 businessPath、requiredAssertions、suggestedTestLayers， 以及覆盖率缺口。不要在风险未明确前写业务用例。 不适用：写业务用例、写测试代码、修改产品代码。.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# QA Risk Analyzer — 风险分析
> **CLI 调用约定**：本工具包的 CLI 是 `quality-assurance-agent/scripts/qa_agent.py`。
> 它**不以 PATH 命令的形式分发**——命令由你（agent）执行，人不必手敲。
> 开工前解析一次 skill 目录，之后所有命令一律写成
> `python "$QA_AGENT_DIR/scripts/qa_agent.py" <cmd>`：
>
> QA_AGENT_DIR="${QA_AGENT_CLI:-$(dirname "$(find ~/.claude/skills ~/.agents/skills ~/.codex/skills .claude/skills .agents/skills .codex/skills -maxdepth 2 -name SKILL.md -path '*quality-assurance-agent/*' 2>/dev/null | head -1)")}"
>
> 运行环境若已告知本 skill 目录（Claude Code 会），直接用，不必跑上面的查找。
> 完整命令语法见 `$QA_AGENT_DIR/references/cli-reference.md`。
## 你的定位
你的任务是**在写用例之前先找 bug 思路**。如果你跳过这步直接写用例，用例会变成机械覆盖 API 参数而非针对业务风险的防守性测试。
你的产出不是"一个必须交的 JSON 文件"，而是后续 `qa-testcase-designer` 的判断依据——每条 P0/P1 风险必须要么有一条对应用例，要么是一条明确记录的 open question。
你不上手修代码，不自己跑测试，不做 Ready 判定。
## CLI 命令
本阶段所有命令的完整语法、参数说明见**主 skill（quality-assurance-agent）→ CLI 命令参考 → 阶段 1**。这里不重复维护命令语法。
## --module 参数的使用约定
这是本阶段最关键的一个参数选择：
- **验收已有模块**：**必须带 --module**，逗号分隔列出目标代码文件（绝对路径、相对路径、目录路径或 glob）。这样 `affectedFiles` 只包含你真正关心的代码，不会混入全仓库 160 个无关文件。
- **开发新功能、有 git diff**：不带 --module，工具会自动从 git diff 提取变更文件。
…Read the whole file at its exact version.
How to install
mdr add mingdui/ming-qa/qa-risk-analyzer@git:20260920.56e926fmdr add mingdui/ming-qa/qa-risk-analyzer@sha256:11dfd34e868b6148Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_mjragal2jw62ilcr)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260920.56e926f latest | 2026-09-20 | 56e926f | 7,480 B | A | view · diff |
| git:20260918.2d0e957 | 2026-09-18 | 2d0e957 | 7,471 B | A | view · diff |
| git:20260918.8d4fb77 | 2026-09-18 | 8d4fb77 | 7,481 B | A | view · diff |
| git:20260916.d5f28f3 | 2026-09-16 | d5f28f3 | 7,028 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7480 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
mingdui/ming-qa · 28 stars · license MIT · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_mjragal2jw62ilcr GET https://markdownregistry.com/api/v1/resolve?ref=mingdui/ming-qa/qa-risk-analyzer GET https://markdownregistry.com/api/v1/blob/11dfd34e868b61482e385b77bc3b118ed18cfc5577d2dfda6e7357ffe5a4739b
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.