QAwalk

All guides › By agent

By agent

QA with Claude Code: install the skill, ask in plain words, read the canvas

How Claude Code runs QAwalk: the skill it installs, what it may do without asking, what it asks first, the prompts that work, and how it reads reviewer feedback and the inbox.

Claude Code already builds the feature. With the qawalk skill it also walks the acceptance plan, captures the screens, evaluates the criteria and shares the canvas, then reads what the reviewer returned.

The problem

Without a skill the agent improvises QA: it opens the page once, says "looks fine" and moves on. Nobody can see what it looked at.

What changes with QAwalk

The skill tells Claude Code when a walkthrough is due, what "done" means (validated scenario, every step captured or explained, evaluation and build run, the link posted), what it may do without asking (local and review environments, test data there, scenario mechanics) and what needs a person first (changing acceptance criteria, any production run, uploading).

How it works

  1. Install

    npm install --save-dev github:sinfin/qawalk#v0.1.0, then npx qawalk init --agent claude --org <your-org> copies the skill to .claude/skills/qawalk and creates qawalk.config.yml. npx qawalk doctor checks Chrome, token, environments and the evaluator key.

  2. Ask

    "Walk the acceptance plan of TASK-123 on local and share the result." The skill routes to its references: acceptance, execution, evaluation, environments, collaboration.

  3. Drive the browser your way

    Claude Code uses the shared browser through a Playwright step script or a browser tool over MCP (the CDP endpoint is printed by qawalk browser start).

  4. Close the loop

    after sharing, the skill reads qawalk feedback and qawalk inbox before continuing on the task. Optionally connect the MCP server so the agent reads runs and feedback as tools.

Skills and prompts

Walk the acceptance plan of TASK-123 with QAwalk on local and share the result into the PR.
What did the reviewer return on the last run of TASK-123? Fix it and run again.
Compare the latest run of checkout with the baseline and explain the differences.

Expected outcome in each case: the commands the skill prescribes, a summary line, failing or unreviewed criteria with evidence, and links to the canvas; no production run without asking.

What you get

FAQ

Does Claude Code need a browser tool?

No. Scripted steps run through Playwright inside the CLI; for judgement-driven steps a browser MCP or computer use helps, but qawalk capture --url works from the shell alone.

What does the agent send to the AI evaluator?

Only a reduced text outline of each page with e-mails and tokens masked, and only for criteria marked semantic. Screenshots and raw HTML never leave your machine except to your own QAwalk organization.

What it looks like

A real run of QAwalk on its own public pages, refreshed daily. This is the canvas your team gets.

6 of 6 steps passed · 2026-09-24Open the run in QAwalk ↗

More guides

QA with Codex: the skill in skills/qawalk and a pointer in AGENTS.mdQAwalk in CI: headless runs, read-only tokens, one comment per scenario

Install in three steps

QAwalk runs where your code and your agent are. The service stores and versions the results, shows the canvas and collects approvals.

  1. Add the CLI to the project
    npm install --save-dev github:sinfin/qawalk#v0.1.0

    Pre-launch: the repository is private. Ask Sinfin for access.

  2. Create the config and install the skill
    npx qawalk init --agent claude --org <your-org>
npx qawalk doctor

    The skill is copied to .claude/skills/qawalk.

  3. Create your organization and a token

    Create an organization; you become its admin. The start page offers a tester token in one click, later under Settings → API tokens. Put it into the project .env:

    QAWALK_TOKEN=qwk_…
TYPESAFE_API_KEY=…   # optional: semantic evaluator
  4. Run and share
    npx qawalk start --scenario docs/tasks/TASK-123/qa/scenario.yml --env local
npx qawalk walk        # playwright steps; agent/manual steps: qawalk capture
npx qawalk evaluate
npx qawalk share --pr

    Or ask your agent: “Walk the acceptance plan of TASK-123 with QAwalk on local and share the result.”