qa-context-profiler skillA
qa-context-profiler is agent-read markdown (skill) from mingdui/ming-qa: QA 上游阶段——为仓库构建事实画像和环境证据。当你需要收集模块的代码上下文、索引已有用例和测试、 检查前后端服务可达性、准备环境快照时触发。只收集事实，不做风险分析、不写用例、不判断质量。 通常在 quality-assurance-agent 的调度下作为第一阶段执行。 不适用：风险分析、用例设计、测试执行、质量判定（由下游阶段负责）。.
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 Context Profiler — 上下文收集
> **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`。
## 你的定位
你是 QA 流程的第一个执行阶段。你的任务很窄：**收集事实，不做判断**。
你不分析风险、不设计用例、不写测试代码、不判断代码质量、不给出就绪结论。
你产出的是后续所有阶段依赖的原材料——context、已有用例索引、环境快照。如果原材料有缺失或错误，整个 QA 管道都会跑偏。
## CLI 命令
本阶段所有命令的完整语法、参数说明、flag 含义见**主 skill（quality-assurance-agent）→ CLI 命令参考 → 前置准备 + 阶段 0**。这里不重复维护命令语法。
## 工作流（按顺序执行，不要跳过）
### 1. 确定 scope
用户可能提了具体的需求文档、模块名、diff 范围、branch、commit、或业务流程。从对话中提取 scope 边界。如果 scope 不明确，先问清楚——你不能靠猜来决定收集哪些代码文件。
### 2. 初始化项目布局
如果 `.qa-agent/config`、`.qa-agent/cases`、`.qa-agent/local`、`.qa-agent/current` 任一目录缺失，先跑 `init-project --repo .`。
不要假设目录已经在——检查后再决定。
### 3. 加载项目经验
运行 `show-knowledge` 加载两类经验：
```bash
…Read the whole file at its exact version.
How to install
mdr add mingdui/ming-qa/qa-context-profiler@git:20260918.2d0e957mdr add mingdui/ming-qa/qa-context-profiler@sha256:59ccffe07ffdd12aPin 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_ubmgfoqmglqryzpn)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260918.2d0e957 latest | 2026-09-18 | 2d0e957 | 7,396 B | A | view · diff |
| git:20260918.568ef46 | 2026-09-18 | 568ef46 | 7,406 B | A | view · diff |
| git:20260918.8d4fb77 | 2026-09-18 | 8d4fb77 | 7,456 B | A | view · diff |
| git:20260916.d5f28f3 | 2026-09-16 | d5f28f3 | 6,898 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 (7396 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_ubmgfoqmglqryzpn GET https://markdownregistry.com/api/v1/resolve?ref=mingdui/ming-qa/qa-context-profiler GET https://markdownregistry.com/api/v1/blob/59ccffe07ffdd12ad96cafc941ff6c60b0def757cbb4fb8ab015b10429cf870c
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.