comment-cleanup
Clean up code comments. Use when: improving comment quality, removing redundant comments. Triggers on: 'clean up comments', 'comment cleanup'.
Skills
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 10-26 00:15
Testing & quality
12,705 results
vue-composable-testing
Test Vue 3 composables with Vitest following best practices. Use when writing tests for composables, creating test helpers for Vue reactivity, or when asked to…
craft-experiment-readout
Summarize experiment results, call a winner, and draft a stakeholder-ready recommendation. Use when an A/B test is complete and you need to communicate results.
traits
This skill should be used when the user asks about "Effect Equal", "Effect Hash", "Equivalence", "Order", "structural equality", "custom equality", "comparing…
laravel-testing
Laravel testing with PHPUnit and Dusk, feature tests, unit tests, browser tests, factories, assertions. ALWAYS activate when: writing tests, tests/Feature/,…
skill-creator
Create, edit, evaluate, and debug the skills in this repo, including running their evals and fixing a description that fails to trigger. Use when user says…
qa-engineer
Expert QA engineer for test strategy and automation. Use when writing tests, fixing failing tests, or improving test coverage.
setup-mac2
Prepare and verify Appium Mac2 for native macOS automation by validating Node/Appium, macOS and Xcode tooling, driver installation, doctor output, privacy…
setup-safari
Prepare and verify Appium Safari on macOS by validating Node/Appium, Safari and safaridriver prerequisites, driver installation, optional doctor behavior,…
quality-gate-orchestrator
Tracks required validation gates, records pass/fail/waived results, and reports readiness before task completion.
testing-strategies
Comprehensive testing strategies with Vitest, Jest, and Testing Library
global-review
Runs parallel reviews (simplification, security, code quality) on the current diff and generates a consolidated report with diffs and explanations.
shaders
This skill should be used when the user asks to "write a custom Three.js shader", "create a GLSL shader effect", "build a TSL shader", "debug a WebGL or WebGPU…
Testing
Smart contract testing with Foundry — unit tests, fuzz testing, fork testing against live state, and invariant testing. What to test, what to skip, and what…
browser-automation
Browser testing, design-to-code conversion, accessibility auditing, and visual debugging. Use for web development, testing, and design implementation.
arxiv-watcher
Search and summarize papers from ArXiv. Use when the user asks for the latest research, specific topics on ArXiv, or a daily summary of AI papers.
code-review
Systematic code review patterns covering security, performance, maintainability, correctness, and testing — with severity levels, structured feedback guidance,…
critical-code-reviewer
Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code",…
playwright-browser-automation
Direct Playwright API for browser automation without MCP complexity. Navigate websites, interact with elements, extract data, take screenshots, generate PDFs,…
swiftui-performance-audit
Audit and improve SwiftUI runtime performance from code review and architecture. Use for requests to diagnose slow rendering, janky scrolling, high CPU/memory…
verify-runtime
Use when modifying data-flow code (API calls, dual-write, mutations, database reads/writes) to verify runtime behavior via structured dev logs, before claiming…
diagnose
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user…
code-review-excellence
Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when…
circleci-smarter-testing-onboarding
Onboard a project onto CircleCI Smarter Testing — write `.circleci/test-suites.yml`, replace the raw test step (or legacy `circleci tests glob`/`split`/`run`)…