使用方法
- 复制安装命令，在自己的智能体环境安装前先检查源码包。
- 从原始文档核对所需工具、凭据和支持的宿主。
- 说明输入材料与期望交付物，并对照来源检查输出。
npx skills add https://github.com/sociuu/sociuu-skills --skill sociuu-aq开始前需了解
- 安装不包含模型订阅、API 额度或访问文件的权限。
- 仓库星数和安装量反映活跃情况，不等于独立质量或安全测试。
按源仓库内容呈现，保留标题、案例、代码、表格、链接以及原文引用的演示图片。
Sociuu AQ
Run only on explicit request or an accepted recommendation identifying the exploratory gap. A generic checklist does not authorize AQ. State the bounded journeys/personas and reuse available evidence. Playwright can complement AQ; standalone exploration need not build a new test framework or run unrelated lanes.
Prepare
Read the canonical QA Runbook and Ledger through sociuu-task. Check applicable tenant, role, configuration and synthetic data cases, plus independent API or persisted-state assertions for data-dependent outcomes. Extend concrete gaps. A missing required capability is blocked, not not-applicable.
- Confirm task worktrees and exact environment binding through dock (or the
sociuu-dock compatibility entrypoint). Reuse a healthy matching environment.
- Check personas/scenarios against current Apex Scaffolding output. Read its
owning skill/module documentation in the bound Apex checkout when setup must change. Reuse verified data; route missing synthetic coverage to that owner. Never insert ad hoc rows or use Production data to conceal a missing scenario.
- Invoke compound-engineering:ce-dogfood directly with the existing Dock URL,
runbook, personas and relevant repository diffs. Use its phase reference, checkpoint and report; agent-browser owns browser interaction. Do not start a generic replacement server or claim one repository diff covers others.
Reconcile
Dogfood may perform its permitted small fixes. Any source change requires normal product tests and affected review, and reconciliation of Dock images/source before retesting. Record exact tested sources, report, findings and coverage gaps in the Ledger; add new scenarios/results to the QA Runbook. Keep skipped and blocked acceptance visible. A completed report is not proof that every criterion passed.
Dock owns runtime/database lifecycle; Apex owns synthetic data; CE owns exploration. This skill grants no merge, deployment, Production or additional message authority. It introduces no GateHouse, custom browser framework or second QA state machine.
