quality
Comprehensive quality assurance and functionality verification. Edge case testing and code quality audit.
Best use case
quality is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Comprehensive quality assurance and functionality verification. Edge case testing and code quality audit.
Teams using quality should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/quality/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How quality Compares
| Feature / Agent | quality | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Comprehensive quality assurance and functionality verification. Edge case testing and code quality audit.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Quality Skill Meticulous QA and verification. ## When to Activate This skill is relevant when: - Verifying implementation correctness - Running comprehensive QA checks - Testing edge cases and error handling - Final pre-commit quality audit ## Core Principles ### Trust Nothing - Developer says it works - prove it - Test assumptions rigorously - Question happy path focus - Find the bugs before users do ### Edge Case Hunter - Empty inputs - Max length inputs - Network failures - Concurrent operations - Invalid data - Boundary conditions ### Code Quality - Consistency with patterns - Clear naming conventions - No unused code - No TODO comments left behind - No debug artifacts ### Documentation - If not documented with evidence, didn't happen - Screenshots for UI changes - Logs for API changes - Clear reproduction steps ## Quick Checks For quality verification, check: - [ ] Implementation complete (all tasks done) - [ ] Code review passed - [ ] Build passing successfully - [ ] Correctness: Happy path works - [ ] Correctness: Edge cases handled - [ ] Correctness: Error states managed - [ ] Consistency: Follows project patterns - [ ] Cleanup: No unused imports - [ ] Cleanup: No dead code - [ ] Cleanup: No console.log leftovers - [ ] Cleanup: No TODO comments - [ ] Test Quality: Tests are meaningful - [ ] Test Quality: Business logic covered - [ ] Test Quality: Edge cases tested - [ ] Automated tests all pass - [ ] Manual verification complete - [ ] UI components work as expected - [ ] API endpoints respond correctly - [ ] Evidence captured (screenshots/logs) - [ ] Walkthrough documented ## Issue Severity Levels ### Blocker - Prevents core functionality - Data loss risks - Security vulnerabilities - Must fix immediately ### Critical - Major feature broken - Significant bugs - Performance degradation - Fix before release ### Major - Important but not breaking - Workarounds exist - Should fix soon ### Minor - Nice to have fixes - Style issues - Minor improvements
Related Skills
wireframe
Create markdown wireframes with detailed UX descriptions from a product specification. Senior UX Designer perspective inspired by Notion and Linear.
ux_redesign
Redesign a feature or page from a Principal UX Designer's perspective.
tech_review
Senior Principal Engineer performing thorough technical review of implementation plans before development.
tasks
Break down an approved implementation plan into specific, actionable tasks.
specify
Create a product specification that defines what to build and why, without prescribing how.
skeptical_review
Perform a critical, skeptical code review of the project from the perspective of a Principal Engineer.
security_agent
Perform a full security review of the codebase (Node.js & React focus).
review_plan
Review the technical implementation plan against the specification.
review_domain
Perform a thorough architectural review of a domain model.
review_constitution
Review and stress-test the technical constitution after /constitute.
retro
Reflect on the completed feature, document lessons learned, and improve workflows.
release_gate
Final Go/No-Go check and release preparation.