Quality gate
Run a complete code quality and security audit against both checklists. Use when reviewing code, before merging, or when running 'quality gate', 'code quality check', or 'audit code'.From its SKILL.md
npx -y skills add skatekowski/wheee-plugin --skill quality-gateAssembled 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
1.7 KB, as published. Nobody here has run it
Quality Gate
Run a comprehensive quality and security audit against both checklists.
Process
- Read
references/CODE-QUALITY-CHECKLIST.mdandreferences/SECURITY-CHECKLIST.md - Determine scope: What files/modules are being audited?
- If recent changes exist:
git diff --name-only HEAD~1to find changed files - If a specific scope is given: use that
- If no scope: audit the entire project
- If recent changes exist:
- Run each checklist section against the scoped files
- For each finding, include:
- File path and line number
- Severity: CRITICAL / WARNING / INFO
- What's wrong and how to fix it
- Produce a summary report with pass/fail counts per section
Output Format
## Quality Gate Report
### Code Quality (X/12 sections passed)
- [PASS] Section 1: ...
- [FAIL] Section 2: ... (3 issues found)
### Security (X/14 sections passed)
- [PASS] Section 1: ...
- [FAIL] Section 2: ... (1 critical issue)
### Findings (by severity)
#### Critical
- [file:line] — [issue]
#### Warnings
- [file:line] — [issue]
### Verdict: PASS / FAIL
Gate Levels
Adapt the depth based on change size:
- Level 0 (< 3 files): Quick scan — OWASP Top 3, obvious bugs
- Level 1 (3-10 files): Standard — full code quality checklist
- Level 2 (10-30 files): Deep — both checklists, dependency check
- Level 3 (> 30 files): Full audit — everything + architecture review