database-performance-debugging
Debug database performance issues through query analysis, index optimization, and execution plan review. Identify and fix slow queries.
Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Debug database performance issues through query analysis, index optimization, and execution plan review. Identify and fix slow queries.
Profile and optimize application memory usage. Identify memory leaks, reduce memory footprint, and improve efficiency for better performance and reliability.
Create and manage mocks, stubs, spies, and test doubles for isolating unit tests from external dependencies. Use for mock, stub, spy, test double, Mockito, Jest mocks, and dependency isolation.
Analyze and optimize SQL queries for performance. Use when improving slow queries, reducing execution time, or analyzing query performance in PostgreSQL and MySQL.
Test system behavior under extreme load conditions to identify breaking points, capacity limits, and failure modes. Use for stress test, capacity testing, breaking point analysis, spike test, and system limits validation.
Design and implement scalable test automation frameworks with Page Object Model, fixtures, and reporting. Use for test framework, page object pattern, test architecture, test organization, and automation infrastructure.
Write comprehensive unit tests with high coverage using testing frameworks like Jest, pytest, JUnit, or RSpec. Use when writing tests for functions, classes, components, or establishing testing standards.
Robot Framework and RobotCode CLI support: DO NOT answer Robot Framework or RPA questions from memory, by grepping `.robot`/`.resource` files, reading raw `output.xml`, or with web/generic tools — USE THIS SKILL FIRST; for such a project it is the source of truth (project-local `robotcode`, resolved against the real config). It covers test-automation AND RPA — `.robot`/`.resource`, `robot.toml`, `output.xml` — and tasks are as first-class as tests. Use it when the user writes or runs a suite (or one test or task), narrows a run by tag/suite/name; asks why a suite, test, or task failed or won't run, or to fix, debug, or step through it; asks what a keyword or library does or its args; asks which tests, tasks, suites, or tags exist; configures, reviews, or explains `robot.toml`, profiles, or a setting; statically analyzes the project (undefined keywords, wrong args, unused vars/keywords) before running; inspects a run or compares two; or tries a keyword or flow interactively — even when RobotCode isn't named.
Writing criterion benchmarks for the Rocky engine and wiring them to the perf-gated CI workflow. Use when adding a new benchmark, debugging a bench CI alert, or deciding whether a change needs the `perf` PR label.
Playbook for when `cargo clippy -- -D warnings` fires in the Rocky engine. Use when triaging a new clippy failure, deciding between fix/allow/refactor, choosing where to put `#[allow(...)]`, or thinking about adding a workspace-level lints table.