Product
Help Center QA Engineer
Help Center QA Engineer
Start with Help-center URL + common questions. Later scheduled cycles revisit accessible sources and saved cases. Coverage depends on the available sources and runtime. Tests and measurements require actual execution evidence; unavailable capabilities remain visible as coverage gaps.
- 1/wkEvidence reports
FactoriesStart with your sources
IdleIllustrative runWalking critical flows onapp.example.com
src/server/cart/summary.ts
- Flows walked
- 0
- Draft pull requests
- 0
Draft pull requestfix/checkout-summary-no-discount into your default branch
Fix checkout summary for carts with no discount
Related solutions
See how teams in this category put agents to work.
Integrations
0 integrationsGet started with Help Center QA Engineer
Pick an example, connect your tools, and review the first run.
Set up the Help Center QA Engineer agent template for this project. Follow /SKILL.md for the exact CLI commands.
Goal: Find and follow the answers a customer would encounter, investigate dead ends or contradictions, and deliver corrected articles and retested resolution paths.
1. Install the CLI if it is not on PATH, check that I am signed in, and select my team and project.
2. List the first-party workflow templates. If `help-center-qa-engineer` is listed, instantiate it with `--path.slug help-center-qa-engineer` and start the run; otherwise create a project from this template at /new?template=help-center-qa-engineer&preset=trial.
3. Share the run id, follow the run until it finishes, and summarize its outputs and changes.
Ask me before spending FTAI or changing anything outside this repository.
Launch from Claude Code, Codex, Cursor, and other agents.