Use for bun:test syntax, assertions, describe/it, test.skip/only/each, and basic patterns.

Get comprehensive review of a GitLab merge request

Debug and fix bugs, errors, or unexpected behavior

Get comprehensive review of a GitHub pull request

Write tests for code using test-driven development principles

Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle

Orchestrate change control workflow with baseline management, impact assessment, CCB review, and communication

Orchestrate production incident triage, escalation, resolution, and post-incident review using ITIL best practices

Orchestrate living requirements refinement, change control, impact analysis, and traceability maintenance throughout SDLC

Orchestrate architecture evolution workflow with ADR management, architecture review, breaking change analysis, and migration planning

Orchestrate Delivery Track flow with test-driven development, quality gates, and iteration assessment

Orchestrate comprehensive test strategy with test suite execution, coverage validation, defect triage, and regression analysis

Automatically manage regression test baseline lifecycle triggered by releases, deployments, and quality gates

Track and analyze regression statistics, trends, hotspots, and health indicators across test suites

Create and maintain regression test baselines for comparison and drift detection across versioned snapshots

Identify the commit that introduced a regression using git bisect with automated test execution and blame context

Aggregate multi-reviewer feedback into consolidated, prioritized, and actionable recommendations

Analyze large source files and produce decomposition plans, optionally executing refactoring with import updates and test verification

Run multi-stage quality assurance on marketing assets with channel-specific validation and approval-ready reports

Auto-generate test data factories from schemas, types, or models. Use when creating test data infrastructure, setting up fixtures, or reducing test setup boilerplate.

Suggest and apply fixes for flaky tests based on detected patterns. Use after flaky-detect identifies unreliable tests that need repair.

Run mutation testing to validate test quality beyond code coverage. Use when assessing test effectiveness, finding weak tests, or validating test suite quality.

AUTO-INVOKE when user mentions research, paper, citation, GRADE, corpus, provenance, literature review, induct paper, evidence, bibliography. Research framework quick reference — discovery phrases for corpus inception, paper acquisition, GRADE quality, citation graphs, provenance-tracked synthesis.

Detect orphaned tests, obsolete assertions, and test-code misalignment. Use for test suite maintenance, cleanup, and traceability validation.

Verify @file references in AIWG skills and agents against the linking contract — per-file or corpus-wide, with optional auto-fix

Lint and health-check the knowledge base. Finds orphan pages, missing cross-references, stale claims, broken wiki-links, and regenerates the index.

Run the research corpus lint ruleset to detect structural and referential integrity issues — orphan notes, missing frontmatter, broken references, missing GRADE assessments.

Auto-fix discoverable issues

Configure and review npm min-release-age controls for JavaScript projects, including 7-day default gates, 10-day high-sensitivity profiles, npm version requirements, and safe override handling.

Execute Python tests with pytest, supporting fixtures, markers, coverage, and parallel execution. Use for Python test automation.

Execute JavaScript/TypeScript tests with Vitest, supporting coverage, watch mode, and parallel execution. Use for JS/TS test automation.

Generate comprehensive test suite for $ARGUMENTS following project testing conventions and best practices.

Lint @-mentions for style consistency and correctness

Automatically execute tests when code-generating agents modify source files, enforcing the execute-before-return pattern

Project directory path (default current directory)

Scaffold endurance, stress, and adversarial-input tests that reveal degradation rather than immediate crashes

Query and manage the executable feedback debug memory

Expert guidance for browser automation and web testing using Selenium WebDriver with best practices for element location, waits, and test organization.

Cypress end-to-end testing best practices for web applications, covering test structure, commands, and reliability patterns.

Jest testing best practices for JavaScript and TypeScript applications, covering test structure, mocking, and assertion patterns.

RSpec testing best practices for Ruby and Rails applications, covering test organization, data management, and isolation patterns.

Expert in Python testing with pytest and test-driven development

Keeping codebases healthy, performant, and maintainable - refactoring, performance optimization, and technical debt managementUse when "refactor, optimize, performance, technical debt, cleanup, architecture, speed up, bundle size, memory leak, slow query, code smell, complexity, dead code, performance, refactoring, optimization, technical-debt, architecture, cleanup, bundle, memory" mentioned.

Safe code transformation - changing structure without changing behavior. From Fowler's catalog to legacy code strategies, knowing when and how to improve code without breaking itUse when "refactor, refactoring, clean up, legacy code, code smell, improve this, restructure, technical debt, rewrite, extract, inline, rename, move method, refactoring, legacy-code, code-smells, transformation, incremental, technical-debt, clean-code" mentioned.

Strategic technical debt management - understanding the debt metaphor, knowing when to take on debt, when to pay it down, and how to communicate debt decisions to stakeholdersUse when "tech debt, technical debt, legacy code, should we fix, cleanup backlog, maintenance, when to refactor, debt prioritization, shortcuts, tech-debt, technical-debt, legacy, maintenance, prioritization, stakeholder-communication" mentioned.

Build and maintain digital twins - virtual representations of physical systems that synchronize with real-world counterparts for monitoring, prediction, and optimization. Use when "digital twin, virtual model, real-time synchronization, physical-virtual coupling, predictive maintenance, asset modeling, system replica, live simulation, " mentioned.

World-class QA engineering - systematic testing, automation, and the mindset that finds bugs before users doUse when "QA, quality assurance, testing, test automation, e2e tests, integration tests, regression testing, test coverage, playwright, cypress, selenium, test suite, bug report, test strategy, flaky tests, testing, QA, automation, e2e, integration, regression, quality" mentioned.

The art of reviewing code that improves both the codebase and the developer - sharing knowledge, maintaining standards, and building cultureUse when "code review, PR review, pull request, merge request, review comments, LGTM, review feedback, approve PR, request changes, review checklist, code quality, review standards, code-review, pull-request, PR, quality, standards, feedback, collaboration, mentoring" mentioned.

Expert in making the business case for technical debt reduction. Covers quantifying debt costs, getting stakeholder buy-in, prioritizing what to fix, and negotiating engineering time for maintenance. Understands how to translate tech problems into business impact. Use when "tech debt, technical debt, need to refactor, legacy code, maintenance time, engineering capacity, pay down debt, " mentioned.

Expert in the human side of code review. Covers giving feedback that lands, receiving criticism gracefully, navigating disagreements, and building a healthy review culture. Understands that code review is as much about relationships as it is about code quality. Use when "code review, PR feedback, review comments, how to give feedback, harsh review, review culture, constructive criticism, " mentioned.

Expert in running effective incident postmortems. Covers blameless analysis, root cause investigation, action item prioritization, and building a learning culture. Understands that incidents are opportunities to improve systems, not punish people. Use when "postmortem, incident review, what went wrong, root cause, blameless, outage, post-incident, " mentioned.

Expert in protecting projects from scope creep. Covers requirement management, stakeholder negotiation, saying no diplomatically, and keeping projects focused. Understands that scope creep kills more projects than technical debt. Use when "scope creep, feature request, can we also, while you're at it, one more thing, requirements changed, scope management, " mentioned.

Expert in building shareable generator tools that go viral - name generators, quiz makers, avatar creators, personality tests, and calculator tools. Covers the psychology of sharing, viral mechanics, and building tools people can't resist sharing with friends. Use when "generator tool, quiz maker, name generator, avatar creator, viral tool, shareable calculator, personality test, " mentioned.

Comprehensive Git configuration guide covering global settings, aliases, performance tuning, credential management, maintenance, .gitattributes, clone shortcuts, and troubleshooting. Use when configuring Git beyond basic setup, optimizing Git performance, setting up aliases, managing credentials (GitHub CLI, Windows Credential Manager), configuring line ending strategy, setting up .gitattributes, enabling Git maintenance, or troubleshooting configuration issues. Cross-platform guidance for Windows, macOS, and Linux.

Comprehensive guide to GPG commit signing. Set up, configure, and troubleshoot GPG commit signing. Fix GPG signing errors, configure passphrase caching, verify commit signatures. Use when working with Git commit signing, GPG keys, commit verification, signature verification, GPG configuration, or when encountering GPG signing errors. Covers Windows (Gpg4win), macOS (GPG Suite), Linux (gnupg), and WSL installation and setup.

Architecture test guidance for .NET using NetArchTest and ArchUnitNET. Use when enforcing architectural boundaries, testing module dependencies, validating layer constraints, or creating performance fitness functions. Includes code generation templates.

Frameworks for giving and receiving code review feedback effectively. Use for PR comments, review strategies, handling disagreements, and balancing thoroughness with kindness.

Plan test automation strategies including ROI analysis, automation candidate selection, framework evaluation, and maintainable automation architecture.

AI and technology ethics review including ethical impact assessment, stakeholder analysis, and responsible innovation frameworks

Plan comprehensive test data management including synthetic data generation, data anonymization, versioning, and environment-specific strategies.

Create comprehensive test strategy documents following IEEE 829 structure. Plan test approach, scope, resources, and success criteria for software projects.

Batch-fix analyzer warnings with category filtering and interactive review options

Analyze automation ROI for test cases and recommend which tests to automate based on value and effort. Use for prioritizing test automation investments.

Conduct a PCI-DSS scope assessment and compliance review for payment card handling.

Create a test data strategy covering synthetic data generation, anonymization, and environment-specific data management. Use for data privacy compliance and test environment setup.

Generate a well-structured code review comment using Conventional Comments format. Helps give clear, actionable feedback on PRs.

Analyze test pyramid health by examining test distribution across unit, integration, and E2E levels. Use for test portfolio assessment and rebalancing recommendations.

Create a comprehensive test strategy document following IEEE 829 structure. Use for establishing testing approach on new projects or standardizing existing practices.

Create minimal surgical patch plan for targeted fix. Use for small, focused changes rather than full feature implementations.

Analyze a failed E2E test, fix the underlying issue, and verify the fix. Use after /test-e2e reports failures.

Generate a comprehensive bug fix plan with root cause analysis. Use when you have a bug to investigate before implementing a fix.

Generate a comprehensive chore plan from a one-line description. Use for maintenance tasks, cleanup, refactoring, or dependency updates.

Create a GitHub pull request with full context linking back to the original issue. Use after implementation is complete and ready for review.

Analyze a failed test, fix the underlying issue, and verify the fix. Use after /test reports failures.

Run project test suite and report results in structured JSON format. Use to validate implementation before commit or review.

Execute end-to-end test specification and report results. Use after implementation to validate user journeys before review.

Review architecture of current codebase or staged changes

Swift Concurrency review and remediation for Swift 6.2+. Use when: reviewing async/await usage, fixing concurrency compiler errors, adding Sendable conformance, or migrating to structured concurrency.

Refactor SwiftUI views for better architecture with MV patterns. Use when: cleaning up SwiftUI views, splitting long bodies, standardizing Observable usage, or removing inline side effects.

Screen job applications against requirements and score candidates objectively. Use when a user asks to review applications, evaluate candidates, screen resumes, rank applicants, assess qualifications against a job description, shortlist candidates, or build a hiring scorecard.

Generate and run regression tests after code refactoring to verify behavior is preserved. Use when someone has refactored code and needs to confirm nothing broke — especially when existing test coverage is insufficient. Trigger words: regression test, refactor validation, behavior preservation, before/after test, did I break anything, refactoring safety net, snapshot test.

Restructure and optimize alert rules for monitoring platforms (Sentry, PagerDuty, Datadog, OpsGenie). Use when someone asks to "reduce alert noise", "fix alert fatigue", "create alert rules", "set up escalation policies", "tune alerting thresholds", or "create on-call runbooks". Generates platform-specific alert configurations and tiered escalation policies.

Measures cyclomatic complexity, cognitive complexity, and function length across codebases to identify maintenance hotspots. Use when someone asks about code complexity, function length analysis, maintainability metrics, or needs to find the most complex parts of their codebase. Trigger words: complexity, cyclomatic, cognitive complexity, long functions, hotspots, maintainability index, code metrics.

Analyze application logs, server logs, and error traces to identify root causes, patterns, and anomalies. Use when debugging production incidents, investigating error spikes, parsing crash reports, or correlating events across multiple log sources. Trigger words: logs, errors, stack trace, crash, exception, debug, incident, 500 errors, timeout, latency spike.

When the user wants to perform load testing or performance testing using Artillery with YAML-based scenario definitions. Also use when the user mentions "artillery," "YAML load test," "WebSocket testing," "Socket.io load test," "scenario-based load testing," or "artillery run." For JavaScript-based load testing, see k6.

Automate code reviews with CodeRabbit, the AI-powered review tool. Use when a user asks to set up automated PR reviews, configure review rules, integrate with GitHub or GitLab, customize review instructions, or manage CodeRabbit settings.

Run DOM tests without a browser using Happy DOM — fast JavaScript DOM implementation. Use when someone asks to "test without a browser", "Happy DOM", "fast DOM environment for tests", "replace jsdom", "Vitest DOM environment", or "server-side DOM". Covers test environment setup, Vitest/Jest integration, SSR testing, and performance comparison with jsdom.

Craft custom TCP/UDP/ICMP packets with hping3. Use when a user asks to test firewall rules, probe services with non-default flags, measure RTT to a TCP port, map open ports behind an ICMP-blocking host, or simulate packet patterns for network troubleshooting on systems they control.

Run online login brute-force and password spraying with THC Hydra. Use when a user asks to test the login strength of SSH/FTP/HTTP/SMB/RDP services they own, validate a credential list against a target during an authorized engagement, or run a CTF login brute challenge.

When the user wants to perform load testing, stress testing, or performance testing of APIs and websites using k6. Also use when the user mentions "k6," "load test," "performance test," "stress test," "spike test," "soak test," "thresholds," "virtual users," or "VUs." For browser-based testing, see selenium.

Expose local services to the internet through secure tunnels. Use ngrok to share development servers, test webhooks locally, demo applications to clients, and create temporary public URLs for any local port.

Perform network reconnaissance with Nmap. Use when a user asks to scan networks, discover hosts and services, detect OS versions, find open ports, enumerate service versions, or perform initial reconnaissance for a penetration test.

Capture and analyze network traffic with Wireshark and tshark. Use when a user asks to sniff packets, debug a protocol, extract files from PCAPs, inspect TLS handshakes, troubleshoot network latency, or triage a CTF PCAP challenge.

Build a Minimum Viable Product — scope ruthlessly, ship fast, learn from real users. Use when: planning what to build first, reducing scope to essentials, launching quickly to test assumptions.

Test Python code with pytest. Use when a user asks to write unit tests, set up test fixtures, mock dependencies, run async tests, measure coverage, or implement test-driven development in Python.

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 integration tests, or asks for test-first development.