kennyolofsson23-netizen/qa
skills/qa/SKILL.md
Full QA pass: run all tests, check types, catch regressions, write missing tests. Use when the user says "run tests", "QA", "verify changes", "check for regressions", "test everything", or "make sure it works".
testing
Updated Apr 17, 2026
$ install --global
skillsauthnpx skillsauth add kennyolofsson23-netizen/claude-code-config qaInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 17, 2026, 4:53 AM4.6s1 file scanned
SKILL.md
- name:
- qa
- description:
- |
- Full QA pass:
- run all tests, check types, catch regressions, write missing tests. Use when the user says "run tests", "QA", "verify changes", "check for regressions", "test everything", or "make sure it works".
- context:
- fork
- argument-hint:
- scope or focus area (optional)
QA Skill — Full Quality Assurance Pass
Run a complete QA pass on all current changes.
Step 1: Scope the Changes
git diff --name-only
git diff --cached --name-only
Categorize every changed file:
- backend → Python tests
- frontend → JS/TS tests + type checking
- ML → ML invariant tests + auditor check
- config → validate no secrets, correct formats
- tests → run them to make sure they pass
Step 2: Detect Test Framework
Before running anything, detect the project's test setup:
- Python: Check
pyproject.toml,setup.cfg,pytest.ini,Makefilefor pytest/unittest/tox config - Node/JS/TS: Check
package.jsonscripts (test,typecheck), look for jest/vitest/mocha config - Type checking: Check for
tsconfig.json(tsc),mypy.ini/pyproject.toml(mypy) - Linting: Check for eslint, ruff, flake8 configs
- E2E: Check for playwright, cypress configs
- Monorepo: Check for workspace config (pnpm-workspace.yaml, nx.json, turbo.json) — run tests per package
Use the detected commands for all subsequent steps.
Step 3: Run Tests (ALL applicable)
Run the test commands discovered in Step 2. Examples:
pytest -v --tb=short(or whatever the project uses)npm test/pnpm test/yarn testnpx tsc --noEmit/mypy .
If new code has no tests → WRITE TESTS FIRST.
Step 4: Write Missing Tests
For every new function, endpoint, or component without test coverage:
- Create the test file in the appropriate
tests/directory - Write tests covering: happy path, edge cases, error cases
- Run them and confirm they pass
Step 5: Regression Check
Run the FULL suite — not just tests for changed files. Use the same commands from Step 2, but ensure full scope (no path filters).
Step 6: Report
QA PASS REPORT
==============
Scope: [backend/frontend/ML/config]
Tests: X passed, Y failed, Z new tests written
TypeScript: clean/X errors
E2E: ran/skipped (reason)
Regressions: none found / [list]
VERDICT: PASS / FAIL
Step 7: Fix Issues
If FAIL: fix every issue found, then re-run from Step 3. Loop until PASS.
Rules
- This skill produces EVIDENCE, not opinions
- "It should work" is NOT acceptable — run it
- If there's no test infrastructure: build it
- Every QA run must end with a clear PASS or FAIL verdict
Related Skills
kennyolofsson23-netizen/vercel-react-best-practices
development
VerifiedTrustedCommunity
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
SKILL.mdUpdated Apr 17, 2026
kennyolofsson23-netizen/property-based-testing
development
VerifiedTrustedCommunity
Provides guidance for property-based testing across multiple languages and smart contracts. Use when writing tests, reviewing code with serialization/validation/parsing patterns, designing features, or when property-based testing would provide stronger coverage than example-based tests.
SKILL.mdUpdated Apr 17, 2026
kennyolofsson23-netizen/project-init
development
VerifiedTrustedCommunity
Initialize a new project with Kenny's universal conventions and stack-appropriate infrastructure. Use this skill whenever: setting up a new project, creating a new repo, scaffolding a new app, starting fresh on a new idea, 'init project', 'new project', 'set up a new app', 'create a project for X', or any variant of starting a new codebase from scratch. Also trigger when the user says 'bootstrap', 'scaffold', or 'kickstart'. This skill ensures every project gets the same quality gates and conventions while adapting infrastructure to the chosen stack.
SKILL.mdUpdated Apr 17, 2026
kennyolofsson23-netizen/project-alignment
development
VerifiedTrustedCommunity
Align any project with Kenny's global Claude Code setup. Audits test coverage, CI/CD, security, skills usage, and creates a prioritized quality roadmap. Use when opening a project for the first time, after a global setup change, or when the user says "align", "bring up to speed", "audit this project", "quality check", or "what's missing".
SKILL.mdUpdated Apr 17, 2026