Test design, vulnerability assessment, and quality assurance (13K skills)
Prepares medical device quality systems for ISO 13485 audits using six focused questions. Reviews design records, corrective actions, process validation, risk files, post-market monitoring, and management reviews, then summarizes readiness gaps and three priority actions.
Review SOC 2 Type II audit readiness through six questions about controls, the organizational safeguards assessed over an observation period. Identify evidence gaps, control changes, and exceptions, then organize readiness findings and three concrete next actions.
Prepare for ISO 27001 audits by reviewing six areas of an information security management system: audit coverage, risks, access, suppliers, incidents, and management reviews. Summarize evidence gaps, readiness, and three priority actions with owners and timelines.
Plan security programs for growing companies by estimating financial risk and prioritizing controls. Produce compliance roadmaps, budget justifications, incident response plans, vendor assessments, and board reports that connect security decisions to business impact.
Choose checks for cmux changes, add tests that reproduce observable bugs, and verify that Swift test files are included in build targets. It also guides local and CI validation, including evidence that selected tests actually ran.
Trace failing cmux Swift package tests to the commits that introduced them by running older revisions in CI, the automated testing environment. It helps distinguish outdated expectations, code regressions, and intermittent failures, then guides focused fixes and verification.
Debug local web and Electron apps through a persistent Playwright session in js_repl, an interactive JavaScript environment. Reuse browser connections while checking user interactions, visual states, screen sizes, and screenshots after changes.
Analyze git history to map contributors to security-sensitive files, identify reliance on too few people, and find stale areas. Export CSV and JSON results for ownership reviews, graph exploration, and comparison with CODEOWNERS.
Review Python, JavaScript/TypeScript, and Go code for security issues using guidance for the project's languages and frameworks. Get prioritized findings, suggested improvements, or help writing new code with safer defaults.
Analyze a codebase to identify valuable assets, attack entry points, and realistic abuse paths. Produce a concise Markdown threat model that explains risk priorities, distinguishes existing protections from proposed mitigations, and makes assumptions explicit.
Write regression tests that catch recurring bugs in FastMCP changes using pytest. Covers reproducing failures before a fix, testing requests without a network server, and checking outgoing requests while replacing external services with test substitutes.
Assess FastMCP vulnerability reports by preserving evidence, reproducing claims, and identifying which component owns the failed protection. Establish affected versions and realistic impact, review proposed fixes, and recommend how the report should be handled.
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.
Add Storybook stories, examples of component states, for the Kilo VS Code extension UI. The existing Playwright runner turns them into screenshot comparisons to check visual changes across states and widths.
Analyze repeated CI test runs to find tests that pass and fail without code changes. Summarize failure rates, investigate likely causes, and recommend fixes, monitoring, or temporary exclusion based on the available evidence.
Coordinate QA agents to plan testing for a game development sprint or feature. Produce test cases, collect results from human testers, document bugs and visual evidence, and prepare a sign-off report based on recorded findings.
Check a game build before handing it to QA, the team responsible for quality checks. Run automated tests, review coverage gaps, confirm critical paths with the developer, and produce a report with results and unresolved checks.
Prepare a long play session with timed observation checkpoints and logs for memory growth, stability, and player fatigue. It creates the testing protocol and analysis template; a human plays the game and records the findings.
Generate reusable test helpers for Godot, Unity, or Unreal projects. Create utilities for checking results, building test objects, and replacing dependencies, following the project's configured test framework and existing test patterns.
Review test files and manual verification records for development tasks. Check whether expected behavior, edge cases, screenshots, and required approvals are covered, then report evidence gaps and distinguish completion blockers from advisory improvements.
Set up automated testing before implementation begins. Detect the configured game engine, create test folders and runner configuration, and prepare a GitHub Actions workflow so tests can run automatically on each push.
Create a game development test plan for a sprint, feature, or individual task. Classify the work and specify automated tests, manual checks, basic functionality checks, and playtest needs from documented requirements.
Turn game bug descriptions or suspected code problems into structured reports with reproduction steps, severity, and priority. Follow reported bugs through fix verification and closure, recording test results or manual checks before marking an issue closed.
Compare existing game tests with key paths in the game design document, find fixed bugs without tests to catch recurrence, and identify coverage gaps from new features. Maintain a release checklist of existing tests.