qa-checklisted

# Skill: qa-check (Global) ## When to Use Run `/qa-check` on any web project to audit for Accessibility (WCAG 2.2 AA), Performance, and Code Quality issues. This skill auto-detects the tech stack and adapts its checks accordingly. Use `$ARGUMENTS` to scope the audit to a specific directory or file pattern (e.g., `/qa-check src/components/`). If empty, audit the entire project. Do NOT fix issues - only report them. Present findings as structured Markdown tables. ## Method ### Phase 0: Stack Detection Before running any checks, detect the project's tech stack by scanning the working directory for marker files. Report what was detected before proceeding. #### Detection Rules Scan in this order. A project can match **multiple** stacks (e.g., WordPress with Node build tools). | Stack | Marker Files | |---|---| | **WordPress / PHP** | `wp-config.php`, `composer.json` with `"wordpress"`, `style.css` containing `Theme Name:`, `functions.php`, `wp-content/` or `content/` directory | | **Python** | `requirements.txt`, `pyproject.toml`, `setup.py`, `setup.cfg`, `Pipfile`, `manage.py` (Django), `app.py` or `wsgi.py` (Flask) | | **Node / JS** | `package.json` - then inspect for framework indicators: `next` (Next.js), `express` (Express), `nuxt` (Nuxt), `@angular/core` (Angular), `react` (React), `vue` (Vue), `svelte` (Svelte) | | **Static Web** | `*.html` files in root or `src/`, `*.css` files, no backend markers detected | #### Detection Output Print a summary before running