bmad-testarch-test-review
Review test quality using best practices validation. Use when user says "lets review tests" or "I want to evaluate test quality"
- License 许可
- AGPL-3.0
- 所属仓库
- Wizarck/nexandro
- 最近更新
- 2026-09-25
- Stars
- ★ 2
- Forks
- 1
01 前言 Front Matter
- name
- bmad-testarch-test-review
- description
- Review test quality using best practices validation. Use when user says "lets review tests" or "I want to evaluate test quality"
02 资源文件 24
- 参考文档bmad-skill-manifest.yaml12 B
- 参考文档checklist.md15.1 KB
- 其他customize.toml1.8 KB
- 参考文档instructions.md1.2 KB
- 脚本scripts/resolve-customization.py6.1 KB
- 参考文档steps-c/step-01-load-context.md6.2 KB
- 参考文档steps-c/step-01b-resume.md3.1 KB
- 参考文档steps-c/step-02-discover-tests.md3.5 KB
- 参考文档steps-c/step-03-quality-evaluation.md7.5 KB
- 参考文档steps-c/step-03a-subagent-determinism.md6.0 KB
- 参考文档steps-c/step-03b-subagent-isolation.md3.5 KB
- 参考文档steps-c/step-03c-subagent-maintainability.md2.8 KB
- 参考文档steps-c/step-03e-subagent-performance.md3.5 KB
- 参考文档steps-c/step-03f-aggregate-scores.md8.3 KB
- 参考文档steps-c/step-04-generate-report.md2.9 KB
- 参考文档steps-e/step-01-assess.md1.2 KB
- 参考文档steps-e/step-02-apply-edit.md1.1 KB
- 参考文档steps-v/step-01-validate.md1.4 KB
- 参考文档test-review-template.md12.1 KB
- 参考文档validation-report-20260127-095021.md2.0 KB
- 参考文档validation-report-20260127-102401.md3.6 KB
- 参考文档workflow-plan.md370 B
- 参考文档workflow.md1.1 KB
- 参考文档workflow.yaml1.6 KB
03 SKILL.md 正文
Available Scripts
scripts/resolve-customization.py-- Resolves customization from three-layer TOML merge (user > team > defaults). Outputs JSON.
Resolve Customization
Resolve inject and additional_resources from customization:
Run: python3 scripts/resolve-customization.py bmad-testarch-test-review --key inject --key additional_resources
Use the JSON output as resolved values.
- Inject before -- If
inject.beforeresolved to a non-empty value, prepend it to your active instructions and follow it. - Available resources -- Note the
additional_resourceslist. Do not read these files now; they are available for the injected prompt or workflow steps to reference when needed.
Follow the instructions in workflow.md.
Post-Workflow Customization
After the workflow completes, resolve inject.after from customization:
Run: python3 scripts/resolve-customization.py bmad-testarch-test-review --key inject.after
If resolved inject.after is not empty, append it to your active instructions and follow it.
04 同仓库更多 Skills
xlsx
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file; create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files into proper spreadsheets.
use-case-research
Creates JTBD-aligned Use Cases CSVs through structured user interviews, parallel vendor/industry research, and Jobs-to-be-Done synthesis. Generates 17-column CSV (OFFER-001 format) and validates with /qa-use-cases. Use when creating or updating use case research for an offering.
sync-jira
Two-way sync between PROGRESS.md pipeline status and JIRA CIT tasks. Use when syncing offering progress with JIRA, checking JIRA status, bootstrapping JIRA tasks for new offerings, or pushing/pulling status updates. Also use when the user mentions JIRA, CIT tasks, or pipeline sync.
strategy
Tunes business strategy and aligns with corporate ABC Goals. Use when working on 01_BS/ business strategy files.
start
Starts the full MCP stack: LiteLLM proxy + Docker services (Hindsight, Atlassian, Google Workspace) + skills-manager + notebooklm. All services connect directly — no proxy. Use /start at the beginning of any session where MCP tools are needed, or when any service is stopped. LiteLLM must start before Docker — Hindsight depends on it at startup.
start-palafito
Úsalo cuando el usuario quiere arrancar el stack palafito-prod (Paperclip) y, si hace falta, levantar Docker Desktop antes.