Stats
Actions
Tags
From QA My App
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/qa-catalog:scanWhen to use
Use when the catalog has drifted too far for an incremental sync, when the test-author template has been changed, or after adjusting task depth settings. Trigger phrases include "force rescan", "regenerate all tests", "full rescan", "redo all tasks", "rescan everything", and "regenerate catalog".
This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
- Framework: !`node "${CLAUDE_PLUGIN_ROOT}/scripts/detect-framework.mjs"`
node "${CLAUDE_PLUGIN_ROOT}/scripts/detect-framework.mjs"test -f QA-tests/catalog.json && echo YES || echo NOIdentical to /qa-catalog: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}.
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-catalog:route-discoverer, qa-catalog: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-catalog:init except:
QA-tests/ already exists. Instead, back up the current QA-tests/tasks/ folder to QA-tests/.qa-catalog/backup-<timestamp>/ before overwriting.qa-page-analyzer (project-level) and test-author, ignoring fingerprints.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-catalog:init does.
After the rescan, print the same summary as /qa-catalog:init plus the backup location.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub elwizard33/qa-my-app --plugin qa-catalog