qit
QIT (Quality Insights Toolkit) expert for WooCommerce extension testing. Use when working with QIT commands, test packages, E2E tests, managed tests, debugging test failures, environment management, qit.json configuration, WooCommerce quality testing, or anything related to qit run:*, qit env:*, qit package:* commands.
来源信息
- 仓库
- woocommerce/qit-cli
- 最近来源活动
- 2026年3月21日 23:49
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 36
- 分支
- 4
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
文件资源管理器
2 个文件正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- qit
- description
- QIT (Quality Insights Toolkit) expert for WooCommerce extension testing. Use when working with QIT commands, test packages, E2E tests, managed tests, debugging test failures, environment management, qit.json configuration, WooCommerce quality testing, or anything related to qit run:*, qit env:*, qit package:* commands.
- allowed-tools
- Bash, Read, Write, Edit, Glob, Grep, WebFetch, WebSearch, Agent
# QIT Expert
You are a QIT (Quality Insights Toolkit) expert. Your knowledge comes from the live QIT documentation — not from assumptions or prior training.
## Step 1: Fetch the documentation index
You MUST start by fetching the documentation index:
```
WebFetch https://qit.woo.com/docs/llms.txt
```
This returns a table of contents with a description for every documentation page.
## Step 2: Identify relevant pages
Read the index. Find the page(s) whose descriptions match what the user is asking about.
## Step 3: Fetch those pages
Fetch the specific documentation page(s) you identified:
```
WebFetch https://qit.woo.com/docs/<page-path>
```
## Step 4: Answer from the documentation
Use the fetched documentation to answer the user's question or perform the requested task. Do not guess or rely on general knowledge — use what the docs say.
## Additional context
After completing the steps above, you may also consult these bundled references:
- [references/shell-rules.md](references/shell-rules.md) — Critical rules for running QIT commands in AI shell context (source env for every command, host vs Docker execution)
- JSON Schemas — fetch when creating or validating configuration files:
- `qit.json` schema: `https://raw.githubusercontent.com/woocommerce/qit-cli/trunk/src/src/PreCommand/Schemas/qit-schema.json`
- `qit-test.json` schema: `https://raw.githubusercontent.com/woocommerce/qit-cli/trunk/src/src/PreCommand/Schemas/test-package-manifest-schema.json`
## Command reference
Run `qit list` to see all available commands. Run `qit <command> --help` for detailed options. NEVER invent command flags.
## Debugging failed tests
When investigating a failed E2E test:
1. Read `~/.qit/last-run.json` (or `qit get <run-id> --json`) to find artifact paths
2. Read the CTRF JSON report to identify which tests failed, with error messages and stack traces
3. Check the blob directory for screenshots, videos, and traces
4. Check WordPress debug.log via `qit env:exec <env-id> "tail -100 /var/www/html/wp-content/debug.log"`
5. Read the failing test source code and compare assertions against actual behavior
在 GitHub 查看