Test design, vulnerability assessment, and quality assurance (13K skills)
Guides feature development and bug fixes by writing tests before implementation. It confirms each test fails for the expected reason, adds only enough code to pass, and checks the full test suite before completion.
Replace TypeScript type assertions in tests with functions from @total-typescript/shoehorn. Use partial objects when only a few properties matter, or deliberately invalid data for error tests, then run a type check to verify the migration.
Build features or fix bugs by writing one failing test, then the smallest implementation that passes it. Tests check behavior through public interfaces, the entry points callers use, so they remain useful when internal code changes.
Set up Claude Code hooks that block Git commands such as push, hard reset, and forced deletion before execution. Choose project-wide or global settings, customize the blocked commands, and verify that the hook rejects a test command.
Inventory existing tests and identify gaps. Link requirements, business rules, risks, and bugs to stable test identifiers and executable evidence, maintaining a test registry that shows what is covered and what still needs verification.
Track module dependencies and verification commands in REGRESSION.md. After a change, check the affected module and downstream consumers, then report command exit codes as evidence that existing behavior still works or needs attention.
Check the full connection between a local agent API and a remote sandbox through a temporary tunnel. Run a task that needs no connected tools, verify its response, and restore the web app’s original API connection.
Review MCP configuration without running its servers. Identify npm, Python, and Docker references that may fetch different code later, classify their version settings, and recommend pinning versions or image contents that the team has reviewed.
Plan and verify security controls for AI agents that read untrusted content and use tools. Review permissions, file boundaries, network destinations, and credentials, then test that rejected actions leave no unintended changes.
Make Swift code easier to test by separating file access, networking, and external APIs behind small protocols. Replace those dependencies with mocks, controlled test substitutes, to check normal behavior and error handling with Swift Testing.
Find remotely reachable security flaws in repository code and assess whether they warrant a vulnerability report. The workflow checks scope, traces attacker-controlled input, confirms impact with a minimal proof of concept, and structures findings for disclosure.
Verify completed code changes in six stages: build, type checks, lint, tests with coverage, searches for possible secrets, and diff review. Produces a pass/fail report with issues to fix and readiness for a pull request.
Develop Spring Boot features and fixes by writing tests before implementation. Guides unit, web, persistence, and integration testing with JUnit 5, Mockito, MockMvc, and Testcontainers, plus JaCoCo measurement of how much code tests cover.
Verify Spring Boot changes through builds, static analysis that checks code without running it, tests, coverage checks, and security scans. Review the diff and produce a pass/fail report showing readiness and issues to fix.
Check whether coding agents follow their assigned skills and rules across three levels of prompt support. Generate test scenarios, inspect tool call sequences, and get reports showing compliance scores and the order of observed actions.
Audit Claude Code configuration with AgentShield to find exposed secrets, excessive permissions, unsafe hooks, and prompt injection risks, where malicious instructions influence an agent. Generate reports, apply supported automatic fixes, or create a security-focused starter configuration.
Build end-to-end tests that operate Windows desktop apps through pywinauto and Windows UI Automation, an interface for accessing screen controls. Covers stable element selection, waits, failure screenshots, test isolation, and CI setup for native applications.
Review security measures in Java Spring Boot services, including identity checks, access permissions, input validation, and secret storage. Provides configuration examples and a release checklist covering API request limits, browser protections, logging, and dependency vulnerabilities.
Develop features and fix bugs by running a failing test first, making the smallest passing change, then refactoring. Check at least 80% test coverage and preserve evidence of failures, successful fixes, and verified behavior.
Review authentication, payments, and APIs for security risks using implementation examples and a predeployment checklist. Covers input validation, access permissions, secret storage, request limits, and checks for sensitive information in logs and errors.
Write and run Perl tests with Test2::V0 or Test::More, replace external dependencies with controlled test substitutes, and measure coverage—the code exercised by tests. Guidance covers test-first development, failure diagnosis, and migration between testing modules.
Assess whether an application is ready for production using local files and authorized evidence. Reviews authentication, data, payments, and operations, then reports release blockers, prioritized fixes, and a readiness score without uploading repository contents to an external audit service.
Write Rust unit, integration, and async tests using a test-first workflow. Covers generated test inputs, mock dependencies, performance benchmarks, and coverage checks to assess behavior and identify code that remains untested.
Verify Quarkus services before pull requests or deployment through builds, code analysis, tests, coverage reports, and security scans. The workflow also checks native executables, containers, performance, health endpoints, configuration, and documentation.