Test design, vulnerability assessment, and quality assurance (13K skills)
Review regression coverage and test quality in Apache Pinot when behavior or tests change. Use it to assess whether code changes and bug fixes have relevant tests, including paths that handle different types or null values.
Investigate Pinot tests that fail intermittently in GitHub Actions. Use the skill to produce a report describing the evidence found and likely causes, helping explain failures that do not occur consistently.
Run a named Pinot test class or individual method in the Maven module that contains it. Use it to focus test execution on a specific target within the project's module structure.
Scans a chosen area of Kaku for hidden defects and usability problems using its fix history and alternative user paths. It separates evidence-backed findings from untested possibilities and reports affected paths, severity, and boundaries checked without issues.
Find gaps in how remove-ai-watermarks detects AI origin information and watermarks across new and retained datasets, then verify fixes and check that removable signals are cleared without breaking required image or stream properties.
Check AI watermarks through Google, OpenAI, Microsoft, or Meta verification services. The skill links results to file hashes, identifiers used to verify file integrity, and records separate evidence for each configured account and verification route.
Verify edited code with relevant build commands, type checks, automated code checks, and targeted tests. Finds commands in project configuration, fixes reported problems, and repeats the same checks until they pass.
Write Jest unit tests for component behavior and user interactions. Includes reusable test data builders, mock replacements for dependencies, and test-driven development, where a failing test guides implementation before the code is cleaned up.
Generate a report with predictable output for acceptance tests of disposable executors, or temporary task runners. Retrieve agent settings, run the supplied report script with specified arguments, and publish the resulting file to S3.
Run Nexent daily or manual full test suites on a self-hosted Ubuntu machine, using the appropriate test layer for each check. Keep results and evidence local, and prepare maintenance candidates for local test assets.
Organize Nexent test assets into a traceable chain from requirements and bugs to cases, scripts, and results. Review existing coverage, maintain execution settings, and generate a registry and Excel views for formal testing.
Add and maintain Nexent Python unit tests with pytest. Isolate external dependencies, cover successful behavior, boundaries, and errors, and add regression assertions that detect fixed bugs. Review existing coverage and record test results separately from formal acceptance cases.
Review Apple platform app code for potential App Store rejection issues before submission. Check privacy, payments, safety, performance, and design using guideline references, risk categories, code examples, and a pre-submission checklist.
Write and review unit and integration tests with Swift Testing. Check assertions, asynchronous behavior, and test structure, or convert existing XCTest tests using guidance on modern APIs and project conventions.
Write and configure unit tests, which check individual pieces of code, using Vitest. Replace dependencies with test substitutes, measure code coverage, compare saved outputs, and organize filtered or parallel test runs.
Review an OpenSpec implementation against its specifications, tasks, and design decisions. The skill checks for missing work, uncovered scenarios, and inconsistencies, then produces a prioritized report with concrete recommendations and code references where available.
Review interface code for accessibility, performance, theme support, responsive behavior, and problematic patterns. Receive a scored report with code locations, user impact, severity levels, and prioritized recommendations to guide subsequent fixes.
Scan code for security risks such as injection attacks and embedded secrets, then report findings by severity. Also check whether design documents record security decisions, trust boundaries, and accepted risks.
Routes security work to specialized guides for web and API testing, code review, threat intelligence, and incident response. Helps organize assessments from both attack and defense perspectives, including coordinated testing of detection capabilities.
Test local web applications with Playwright, a browser automation tool. Write Python scripts to check interface behavior, inspect rendered pages, capture screenshots, and collect browser logs, with a helper that manages one or more application servers.
Checks code changes before a pull request by reviewing builds, types, coding rules, tests, potential secrets, and changed files. Produces a report showing results, test coverage, and issues that need fixing.
Accept screenshot baseline changes by running the project's dedicated script, then commit the updated version.json using the project's commit conventions. This provides an explicit command for recording changes to the screenshot comparison baseline.
Review resolved dependency versions and relevant code for security vulnerabilities. Get findings with evidence, impact, and targeted remedies, distinguishing published dependency warnings from exploit paths demonstrated in the project.
Audit a repository or broad subsystem for security, correctness, and maintenance risks. Trace how inputs reach affected behavior, verify suspected defects, and report confirmed findings with severity, triggers, impact, and practical remedies.