Investigate Scout and FTR flaky test failures in Kibana. Use when triaging a failed-test issue, a Buildkite-reported failure, a test path that has been failing intermittently, or any time the user asks to look at a flaky test, deflake a test, or stabilize a test.
No other project uses it yet
21k5mo agoReviewMountCreate a free account to mount
AWS CDK test-coverage reviewer. Use when a PR adds or changes tests (`**/*.test.ts`, `integ.*.ts`, `*.snapshot`) or ships new functionality, branches, feature-flag states, CFN properties, or cross-service behavior that should be tested — deciding first what coverage each change OWES (a unit test? an integ test? both? already covered? exempt?), then judging whether the PR's tests DISCHARGE it: meaningful assertions over non-asserting tests, edge/negative/feature-flag cases, required integ tests, snapshot-as-synthesized-template diffs, deploy-time assertions, and legitimate exemptions.
13k19d agoReviewMountCreate a free account to mount
name: Toolchain tests
description:
Instructions for authoring, structuring, and running toolchain tests using
the file_test infrastructure.
---
# Toolchain tests
## Introduction
This skill provides guidelines and patterns for creating and updating
34k33d agoReviewMountCreate a free account to mount
Guides an agent through reproducing, root-causing, fixing, and validating flaky tests in the PostHog monorepo. Use when a test fails intermittently in CI but passes on rerun or locally, when `hogli ci:insights` or the debugging-ci-failures skill classifies a failure as a flaky test, when given a GitHub Actions URL for a flaky job, when asked to check Trunk Flaky Tests for a test, PR, or master, or when asked to deflake, stabilize, or fix a flaky Jest, pytest, or Playwright test. Core discipline: reproduce locally before changing anything, fix the root cause (never mask it with sleeps, retries, or bigger timeouts), and prove the fix with an N-run validation loop sized to the observed failure rate. Stabilizing is not the only valid outcome — the skill also gates whether the test should exist, so deleting a test that catches nothing real, or re-leveling one that flakes because of the level it runs at, are first-class endings.
41k3d agoReviewMountCreate a free account to mount
Garden the test suite by finding and removing redundant, vacuous, or implementation-coupled tests while preserving useful regression coverage. Use for test audits, test pruning, duplicate coverage, or reducing CI test cost. Supports focused cleanups and coordinated audit campaigns.
80 projects use a version of this
114k1d agoReviewMountCreate a free account to mount
Runs model-level and module-level tests for TensorRT-LLM. First classifies the test scope (module test or model test), then dispatches to the appropriate workflow. Model tests are further classified by type (functionality/smoke test, benchmark, or evaluation). Prompts the user for parallelism parameters (tp, ep, dp), dataset paths, device type, or a config file as needed. All test execution is delegated to trtllm-case-executor.
15k3mo agoReviewMountCreate a free account to mount
Writing unit and integration tests for the tldraw SDK. Use when creating new tests, adding test coverage, or fixing failing tests in packages/editor or packages/tldraw. Covers Vitest patterns, TestEditor usage, and test file organization.
Steady2 mentions in 2 weeks
11 projects use a version of this
51k6mo agoReviewMountCreate a free account to mount
Run and debug Vitess end-to-end tests. Use when working with tests under go/test/endtoend/, when asked to run e2e tests, debug e2e test failures, or investigate test flakiness.
21k4mo agoReviewMountCreate a free account to mount
Testing CKEditor 5 plugins in the Trilium monorepo. Use when adding or reviewing unit tests for the packages/ckeditor5 aggregate (including its in-tree plugins under src/plugins/), debugging a failing test, or setting up a package's test runner. Covers the Playwright browser-mode Vitest setup, the vitest.config.ts, testing against a real ClassicEditor, the model/view helpers imported from 'ckeditor5' (_setModelData / _getModelData / _getViewData and their {}/[] selection syntax), vi spies/mocks, idiomatic patterns for schema/conversion/command/UI tests, the pnpm --filter runner, and Trilium-specific conventions and gotchas. Complements the ckeditor5-plugin-development and writing-unit-tests skills.
Steady11 mentions in 2 weeks
No other project uses it yet
39k26d agoReviewMountCreate a free account to mount
Writes and runs Filament tests with Pest, Pest Browser, accessibility checks, and test databases. Use when planning verification, adding or changing tests, running tests, or validating asynchronous JavaScript changes in this repository.
Steady5 mentions in 2 weeks
No other project uses it yet
33k8d agoReviewMountCreate a free account to mount
Extract a standalone JIT regression test case from a given GitHub issue and save it under a JIT regression runner folder. USE FOR: creating JIT regression tests, extracting repro code from dotnet/runtime issues, "write a test for this JIT bug", "create a regression test for issue #NNNNN", converting issue repro to xunit test. DO NOT USE FOR: non-JIT tests (use standard test patterns), debugging JIT issues without a known repro, performance benchmarks (use microbenchmark skill).
18k2y agoReviewMountCreate a free account to mount
Use when writing, placing or running tests in SolidCraft: a regression test for a bug, an engine test for a command, a UI scenario, a reference (oracle) test, goldens, or when CI fails a test you did not touch.
17k20d agoReviewMountCreate a free account to mount
Run MaterialDesignInXamlToolkit tests correctly with dotnet test, TUnit, and Microsoft Testing Platform. Use when validating changes, choosing a safe test scope, or filtering to the exact affected tests.
Steady11 mentions in 2 weeks
No other project uses it yet
16k4y agoReviewMountCreate a free account to mount
Run Stryker mutation tests on one or a few files and check the HTML report. Invoke when asked to run mutation tests, check mutation score/coverage, or find untested code paths.
28k30d agoReviewMountCreate a free account to mount
Run the Omnigent load test and produce a results file explaining the latencies. Load when the user wants to load-test / stress-test / benchmark Omnigent under concurrency ("load test omnigent", "stress test the server", "how many hosts/sessions/turns can it handle", "load test real agent turns / conversations", "run a load test"). The test makes each simulated user a real omnigent host that creates host-bound sessions and drives real multi-turn conversations with a mocked LLM; it boots its own local stack (dev/loadtest/run.py). Gather inputs, run it, then read the generated summary.md and explain the latency distribution (avg/median/p95/p99, throughput, failures). NOT for single-request latency micro-benchmarks (that is dev/benchmarks/).
Steady11 mentions in 2 weeks
No other project uses it yet
11k27d agoReviewMountCreate a free account to mount
Maintains existing pytest and Django test suites without weakening correctness. Use when asked to reduce Python test runtime or CI work, investigate slow pytest families, remove stale migration tests, consolidate repeated setup, improve Python test ownership, or measure whether a test optimization worked after merge. Ranks work by measured cost, applies the writing-tests value gate to existing coverage, preserves distinct behavior cases, validates isolation after shared-fixture changes, and separates testcase work from pytest-suite wall time. For an intermittent failure, use fixing-flaky-tests instead.
41k3d agoReviewMountCreate a free account to mount
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md or AGENTS.md?
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
What is a skill?
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Can I search my own team's files too?
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.