code-reviewer
Use when the user wants a thorough code review covering security, logic, performance, readability, and best practices with severity-rated findings. Triggers…
Skills
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 10-30 00:12
Testing & quality
12,914 results
debug-diagnostician
Use when the user wants to debug an error by understanding it before fixing it — explanation, root cause hypotheses, evidence, then fix. Triggers include…
sonarqube-fix
This skill should be used when fixing SonarQube quality gate failures. It runs the sonarqube:check skill to identify failures, fixes the identified issues, and…
debugging
Troubleshoot Clay workflow issues, fix common mistakes, resolve auto-update problems, and stop credit waste. Use when the user reports something not working in…
cometchat-flutter-v6-testing
Testing patterns for CometChat Flutter UIKit v6 (stable, Bloc-based). Covers flutter_test + bloc_test for Bloc unit tests, mocktail for SDK mocking, widget…
cometchat-ios-testing
Testing patterns for CometChat iOS UI Kit v5 in Swift / SwiftUI / UIKit projects. Covers XCTest setup, mocking CometChatSDK + CometChatUIKitSwift via…
eng-consolidate-test-suites
Use when adding, moving, reviewing, or auditing tests in Compozy to identify the invariant, owning layer, and canonical suite before changing coverage. Do not…
eng-qa-bootstrap
Bootstraps isolated Compozy QA labs and emits the canonical manifest for downstream QA. Use when local QA needs daemon, workspace, provider, or playbook setup.…
eng-test-conventions
Go test-shape discipline for Compozy. Use when writing or editing *_test.go under cmd or internal after test placement is justified. Do not use for non-Go…
qa-execution
Executes full-project QA like a real user by discovering the repository verification and E2E contracts, running build, lint, test, and startup commands,…
tdd
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants…
accessibility-testing
WCAG compliance testing and accessibility quality assurance workflows for iOS apps. Use when validating accessibility labels, testing VoiceOver compatibility,…
code-review
PR review checklist for datasync-asset-store-filesystem — use when opening or reviewing pull requests.
testing-best-practices
Laravel test design and review. Use when selecting coverage, naming or structuring tests, choosing assertions or test data, isolating dependencies, testing…
verify
Test the full Credyt billing cycle end-to-end for a specific product. Creates a test customer, funds their wallet, sends a usage event, and verifies fees were…
debugging-cypress-artifacts
Debugs Cypress bugs that only reproduce in packaged artifacts (cli/build CLI plus binary-package output), not yarn dev. Covers the git commit/build/clean/…
cs-code-review
Code review gate. Trigger: after implementation is complete, review this round's diff before QA/acceptance/commit.
engine-dev-testing
How to test Dagger engine changes. Covers manual e2e testing via the playground (bootstrapping a dev engine from source, running commands inside it, capturing…
zellij
Terminal workspace and multiplexer for interactive CLI sessions. Use when managing terminal sessions, running interactive REPLs, debugging applications,…
slurm-hpc
Generic Slurm/HPC know-how for any cluster. Use when the user writes or debugs sbatch/srun batch scripts, requests resources…
eval-genius
Decide whether an AI/LLM/agent/retrieval system needs an eval, where it fits in the dev process, which one to run, and how to read the result; then design,…
blender-validation
Blender scene, mesh, material, animation, and export readiness validation
issue-triage
Triage a Deno GitHub issue — reproduce bugs, classify, label, and comment with findings. Use when asked to triage an issue or when an issue number/URL is…
tdd
Implement functionality in a test-driven way. Starting from an agent brief (created by triage) or a PRD, write a failing test → user confirmation → green implementation. Avoid architectural regressions, shallow modules, and excessive mocking.