Scan

Force a full re-scan of every route and rewrite every task, regardless of fingerprints. Use when the catalog drifted too far or when you change the test-author template or task depth. Destructive — overwrites QA-tests/tasks/ after backing them up.From its SKILL.md

Install

npx -y skills add elwizard33/qa-my-app --skill scan

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.6 KB, as published. Nobody here has run it

/qa-my-app:scan — Full rescan

Project context

Framework: !node "${CLAUDE_PLUGIN_ROOT}/scripts/detect-framework.mjs"
Existing catalog: !test -f QA-tests/catalog.json && echo YES || echo NO

Runtime settings

Identical to /qa-my-app:init. Honors ${user_config.parallel_agents}, ${user_config.parallel_test_authors}, ${user_config.browser_channel}, ${user_config.browser_headless}, ${user_config.settle_ms}, ${user_config.auth_mode}, ${user_config.task_depth}, and ${user_config.max_tasks_per_route}.

Instructions

Browser-agent pre-check. Before spawning any page-analyzer agents, verify .claude/agents/qa-page-analyzer.md exists. If not:

mkdir -p .claude/agents

Then read ${CLAUDE_PLUGIN_ROOT}/agents/qa-page-analyzer.md and write to .claude/agents/qa-page-analyzer.md. Do the same for qa-test-runner.md. If the files already exist, leave them unchanged.

When spawning route-discoverer and test-author, use the plugin-namespaced names (qa-my-app:route-discoverer, qa-my-app:test-author). When spawning browser agents, use the project-level names (qa-page-analyzer). All are pre-approved in allowed-tools above.

This skill behaves like /qa-my-app:init except:

It does not stop if QA-tests/ already exists. Instead, back up the current QA-tests/tasks/ folder to QA-tests/.qa-catalog/backup-<timestamp>/ before overwriting.
Re-run every route through qa-page-analyzer (project-level) and test-author, ignoring fingerprints.
Preserve QA-tests/.qa-catalog/backup-*/ so the user can diff manually if a regeneration produced worse tasks.

Use $ARGUMENTS as the dev URL override if provided; otherwise resolve as /qa-my-app:init does.

After the rescan, print the same summary as /qa-my-app:init plus the backup location.