Results for “test”

Quick reference for Salesforce Agent Script CLI commands, covering retrieve, validate, publish, deploy, and test workflows, plus authoring bundle structure and CI/CD integration.

Write, review, debug, test, or optimize Python code using the rustworkx graph library, with explicit handling of graph kind, index lifecycle, payload semantics, and algorithm result mapping.

Runs a relentless interview that sharpens a plan or design and creates docs (ADRs and glossary) along the way. Use when the user wants to stress-test a plan or design, or produce decision records.

Internal harness probe for the OI-3 readability-guidance spike. Use only when explicitly told to invoke spike-probe. Verifies that a freshly-created project skill renders into a subagent's context via the Skill tool.

Configure Hilt dependency injection with proper scoping, modules, and constructor injection in Android. Use when changing the production Hilt graph; defer test overrides, Room wiring, navigation-specific scopes, and generic DI explanations to their specific skills.

Modern Java 21+ language standards including Records, Pattern Matching, and Virtual Threads. Use for Java language constructs or Java-to-Java upgrades; defer Kotlin, tests, formatting/build tools, CompletableFuture, builder patterns, and isolated null-handling questions.

Recommends administering stress-dose glucocorticoids before surgery and tapering after surgery in patients with adrenal insufficiency before repeat testing. Triggers include preoperative planning for surgery in a patient with known or suspected adrenal insufficiency.

Bitcoin Core JSON-RPC interface: authentication (cookie, rpcauth), wallet vs node RPCs, common verbs (getblockchaininfo, getrawtransaction, scantxoutset, importdescriptors, walletprocesspsbt, submitpackage, testmempoolaccept), error handling. USE WHEN: scripting bitcoind, integrating a service, debugging RPC errors.

Configure and maintain Python projects, dependencies, packaging, environments, linting, formatting, type checking, testing, builds, and publishing. Use for pyproject.toml, an existing repository toolchain, or repository-level Python tooling work, not for a standalone script.

Guides the creation of high-quality MCP servers that enable LLMs to interact with external services through well-designed tools, covering planning, implementation, testing, and evaluation.

Enforce writing specifications before any code, with structured formats, acceptance criteria, and validation to reduce rework and clarify requirements.

Modify, build, test, debug, and contribute to the NVIDIA cuOpt codebase (C++/CUDA, Python, server, CI). Includes guidance for solver internals, pull requests, DCO signoff, and code conventions.

Generates Angular code and provides architectural guidance for projects, components, services, and more, covering reactivity, forms, dependency injection, routing, accessibility, animations, styling, testing, and CLI tooling.

Evaluates Expo skills end-to-end: trigger accuracy, generated code quality, and runtime screenshots on iOS simulator and Android emulator via Expo Go.

Simulates BGP hijacking attacks in isolated lab environments to test RPKI deployment, route origin validation, and BGP monitoring defenses against prefix hijacking and route leak attacks.

Designs incremental migration strategies, identifies service boundaries, produces dependency maps and migration roadmaps, and generates API facade designs for aging codebases.

Scaffold and develop AI agents using OpenAI Agents SDK patterns, covering agent definition, tools, guardrails, handoffs, context, RAG pipelines, streaming, API routes, testing, and debugging.

Implements code features phase by phase from a JSON or Markdown plan, with configurable unit-test and quality-gate choices, token-budgeted execution, and resumable state.

Write defensive, portable Bash scripts for automation, CI/CD, and system utilities, with strict error handling, safe argument parsing, and testing via Bats and ShellCheck.

Implements comprehensive backtesting capabilities for Pine Script indicators and strategies. Use when adding performance metrics, trade analysis, equity curves, win rates, drawdown tracking, or statistical validation. Triggers on "backtest", "performance", "metrics", "win rate", "drawdown", or testing requests.

Bun all-in-one JavaScript runtime and toolkit reference. Covers runtime APIs (file I/O, HTTP server, SQLite, shell), ultra-fast package manager, built-in bundler with plugins, test runner with mocking, TypeScript support, and Node.js compatibility.

Build, review, debug, or test declarative statistical visualizations in Python with Altair and Vega-Lite, including chart marks, typed encodings, transforms, parameters, layers, facets, and specification export.

Run shell commands in the background with output capture and completion callbacks. Use when a command might take more than ~30 seconds (builds, tests, deployments, data processing) and you want to keep working while it runs.

Dart static analysis, linting, formatting, and code-generation standards. Use only for analysis_options.yaml, build_runner, dart format, DCM, lefthook, or analyze/format CI failures; defer Dart language, null-safety, Flutter tests, and generic CI questions.

Systematic debugging — reproduce, read the error, isolate, hypothesize, fix, verify, document. Use when tracking down a bug, unexpected behavior, or test failure — including phrases like "this doesn't work", "why is this failing", or "help me debug".

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

Use this when a Python service, package, or repository needs a maintainable internal structure for modules, domain logic, adapters, config, entrypoints, and tests. Trigger on requests about project layout and internal organization for Python systems.

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

Coordinates purple team exercises by running MITRE ATT&CK-mapped attack scenarios with real-time detection testing and collaborative gap remediation.

Detect and exploit Server-Side Template Injection (SSTI) vulnerabilities across Jinja2, Twig, Freemarker, and other template engines to achieve remote code execution during authorized penetration tests.

Collects publicly available information about a target organization to identify attack surfaces, social engineering targets, technology stacks, and credential exposures for authorized security testing.

Select the right Proof of Life (PoL) probe type based on hypothesis, risk, and resources to match validation method to the real learning goal.

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

E2E automation engineer skill for Playwright-driven flow validation, browser interaction coverage, and end-to-end regression checks. Disabled by default for E2E case/spec work; use only when the user explicitly asks for E2E tests or execution.

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.