ac-review
Code Review: Automatically reviews git diff when no arguments are provided, supports reviewing a specified commit by git revision, and generates an execution plan after confirming the remediation scope.
Skills
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 11-02 00:09
Testing & quality
13,028 results
golang-testing
Add, repair, design, or audit Go tests using the standard testing package, table-driven tests, subtests, examples, benchmarks, fuzz tests, race checks,…
verify-quality-simplify
Systematic code simplification. When code becomes complex, duplicated, or overly abstract and needs simplification, or when "simplify", "refactor", "too complex", or "duplicate code" is mentioned
ab-testing
Use when designing and analyzing A/B tests. Suitable for product experiments, feature validation, and conversion rate optimization. Combines hypothesis-driven + sample size calculation + confidence judgment.
acceptance-testing
Used by the business/product side for acceptance before launch. Suitable for feature delivery confirmation, UAT, and pre-launch sign-off. Integrates BDD Given-When-Then, Specification by Example, and ATDD.
bug-reporting
Used when a defect is found and needs to be recorded. Applicable to all defects found in functional testing, regression testing, and exploratory testing. Integrates Cem Kaner's bug reporting, the ISTQB defect lifecycle, and the severity-priority matrix.
code-quality
Use when designing code standards / Lint configurations / Code Review criteria. Covers SOLID principles / Lint tools (ESLint / Prettier / Checkstyle / pylint / golangci-lint) / SonarQube integration. Combines Clean Code + Robert Martin…
competition-queue-worker-drift
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for queues, async workers, cron jobs, delayed tasks, retry behavior, worker-only…
competition-race-condition-state-drift
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for race windows, ordering bugs, idempotency failures, lock gaps, concurrent…
coverage-reporting
Used for test coverage collection and reporting. Suitable for coverage target setting, CI integration, PR comments, and trend tracking.
exploratory-testing
Use when there are no clear use cases or when unknown unknowns need to be discovered. Suitable for first testing of new features, complex business processes, and exploratory spread after Bug fixes. Integrates James Bach SBTM, Elisabeth Hendrickson Heuristics, Tour-Based Testing.
pentest-tools
Active penetration testing toolchain. Covers information gathering, port scanning, vulnerability scanning, web penetration, SQL injection, directory brute-forcing, password cracking, and other scenarios. Exposes 20+ security tools to AI agents via MCP server (pentestMCP / mcp-security-hub). Trigger keywords: penetration testing, port scanning, Nmap, vulnerability scanning, Nuclei, SQL…
performance-testing
Use when evaluating system performance / capacity / load testing. Applicable for pre-launch performance baselines, SLA validation, capacity planning, and performance regression troubleshooting. Integrates Google SRE Workbook, Brendan Gregg USE Method, and k6/JMeter practices.
quality-gate
Used for go-live release decisions / blocking non-compliant deliveries. Applicable to pre-release gates, CI/CD automated gates, and phased quality assessments. Integrates SonarQube Quality Gate, DORA Change Failure Rate, and Google Beyoncé Rule.
regression-testing
Use when avoiding recurrence of old problems after modification/refactoring/Bug fixing. Suitable for version regression, post-fix regression, and refactoring verification. Integrates Impact Analysis, Test Suite Pruning, and the three-tier Smoke/Sanity/Full suite.
test-data-management
Used when preparing test data / data isolation / masking. Suitable for functional test data preparation, performance test data generation, and masked replication of production data. Combines three layers of protection: GDPR compliance, synthetic data, and data isolation.
test-report
Use when outputting test conclusions / making release decisions. Applicable to version release reports, phase summaries, and defect analysis. Integrates ISTQB Test Summary Report, coverage analysis, and defect distribution.
test-strategy
Used when defining test scope, layers, and depth. Applicable to new module test kickoff, release test planning, and pre-launch overall test strategy. Integrates the test pyramid, testing quadrants, and the Beyoncé Rule.
testing-frontend
Used when implementing frontend testing. Covers Vitest / Jest / React Testing Library / Vue Test Utils / Playwright / Cypress / Storybook / MSW / visual regression. Combines the testing pyramid + a11y testing + visual testing.
testing-implementation
Used when implementing unit tests / integration tests / contract tests. Covers JUnit 5 / Jest / Vitest / pytest / Go testing / RSpec / xUnit + Pact contract testing + Testcontainers. Integrates test pyramid implementation + doubles/test doubles + AAA pattern.
testing
Use when running unit tests, debugging test failures, or adding new test cases using Catch2 framework
debug-zoom
Debug a broken Zoom integration by isolating the failure point and routing into the right Zoom references. Use when auth, API, webhook, SDK, or MCP behavior is…
debug-zoom-integration
Debug broken Zoom implementations quickly. Use when auth, webhooks, SDK joins, MCP transport, or real-time media workflows are failing and you need to isolate…
probe-sdk
Reference skill for Zoom Probe SDK. Use after routing to a preflight workflow when testing browser compatibility, media permissions, audio or video…