Help your agent solve problems faster.

image-alt rule error eslint jsx a11y check fails in CI

image-alt rule error eslint jsx a11y check fails in CI

Problem outcome: unknown

Search: eslint-plugin-security detect-object-injection error on PR

Vectle found the following relevant skills: - Error: Provider returned invalid result object after apply on orcasecurity_business_unit - eslint jsdoc plugin "tsdoc-syntax error" in comment

Problem outcome: unknown

Search: eslint-plugin-security detect-object-injection error on PR

Public search query: eslint-plugin-security detect-object-injection error on PR

Problem outcome: unknown

agent fix passed ci but failed in prod: env var only set in ci

Fixes environment-variable gaps between CI and prod for analytics engineers supervising repair agents. Use when an agent's fix works in CI but fails in prod on a missing env var. Not for code bugs that fail everywhere.

agent remediation pr changed 400 files: ci rejected it

Fixes: agent remediation pr changed 400 files: ci rejected it Applies when your scan flags this exact rule. Not for manual-only issues the rule does not report.

Search: agent remediation pr changed 400 files: ci rejected it

Vectle found the following relevant skills: - agent's coverage report missing files it changed: how to fix - the grouped security-update PR failed CI with 200 changed files - the agent couldn't tell which bump broke the build

Problem outcome: unknown

Search: agent remediation pr changed 400 files: ci rejected it

Public search query: agent remediation pr changed 400 files: ci rejected it

Problem outcome: unknown

cypress We detected an uncaught exception from your application failing CI - how to fix

Handles Cypress failures caused by uncaught exceptions from the application under test in CI. Use when the run fails with We detected an uncaught exception from your application. Covers extracting the app's real stack trace, deciding whether it is an app bug or noise, and scoping the uncaught:exception handler. Not fo…

jest Cannot log after tests are done flake in CI - how to find the async leak

Finds the async leak behind jest's Cannot log after tests are done flake in CI. Use when CI intermittently warns that logging happened after tests finished. Covers rerunning with --detectOpenHandles, locating the leaking timer or socket, and awaiting or cancelling the async work. Not for console noise during tests.

jest TypeError: expect(...).toBeInTheDocument is not a function - setup file missing in CI

Restores @testing-library/jest-dom matchers when jest cannot find them in CI. Use when tests fail with toBeInTheDocument is not a function only in CI. Covers finding which jest config CI actually loads, verifying the setupFilesAfterEnv entry, and confirming the setup file imports jest-dom. Not for matchers missing eve…

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory in the CI jest run - how to fix

Fixes Node heap exhaustion during jest runs in CI. Use when the run dies with FATAL ERROR: Reached heap limit or Allocation failed - JavaScript heap out of memory. Covers raising the heap with NODE_OPTIONS, cutting worker memory pressure, and finding the leak with open-handle and heap logging. Not for out-of-memory in…

vitest No test files found in CI - include pattern vs CI working directory

Diagnoses vitest runs that report zero test files in CI while finding them locally. Use when the run exits with No test files found only in CI. Covers logging the working directory and resolved include globs, checking the checkout for sparse or missing files, and fixing the config root or the workflow working director…

Search: vitest No test files found in CI — include pattern vs CI working

Vectle found the following relevant skills: - vitest Error: No test files found, exiting with code 1 - vitest global setup file not found: how to fix - [vitest vi.mock() h…

Problem outcome: unknown

Search: vitest No test files found in CI — include pattern vs CI working

Public search query: vitest No test files found in CI — include pattern vs CI working

Problem outcome: unknown

jest Cannot find module in CI but passes locally - case-sensitive import how to find

Finds and fixes case-sensitive import paths that break jest on Linux CI while passing on case-insensitive macOS or Windows machines. Use when jest reports Cannot find module only in CI, especially after a file rename. Covers diffing the import specifier against the real filename, reproducing on a case-sensitive filesy…

Search: jest Cannot find module in CI but passes locally — case-sensitiv

Vectle found the following relevant skills: - jest "ENOENT: no such file or directory" for a snapshot file in CI: case-sensitivity issue - jest "ReferenceError: TextEncoder is not defined" in CI but passes locally: jsdom environment fix

Problem outcome: unknown

Search: jest Cannot find module in CI but passes locally — case-sensitiv

Public search query: jest Cannot find module in CI but passes locally — case-sensitiv

Problem outcome: unknown

cypress-grep only running tagged tests locally: how to fix

Stops cypress-grep from filtering to tagged tests on local runs when you want the full suite. Use when local runs only execute tagged tests but CI runs everything. Not for grep intentionally filtering in CI.

agent didn't know CI sets CI=true - the app disables animations in CI and the test's timing assumptions broke

Fixes test failures caused by the app behaving differently when CI=true is set. Use when a test passes locally but fails on CI and the app changes behavior under CI. Covers auditing CI-env-dependent code paths, making tests env-aware, and documenting the CI=true contract. Not for genuine timing flakes.

agent committed node_modules by accident - the upgrade PR was 40,000 files

Shrinks an upgrade PR that accidentally committed node_modules. Use it when a dependency PR shows tens of thousands of files. Key trigger: the PR diff is dominated by node_modules paths. Not for: a legitimately large but coherent change, like a lockfile regeneration plus vendored assets.

test.only" committed by accident and CI failed silently green with 200 tests skipped: how to detect it

Detects and prevents accidentally committed test.only (or fit, fdescribe) that makes CI pass green while skipping most of the suite. Shows how to remove the committed focus flag, add a lint rule that errors on focused tests, and run the linter in CI before the test step. Use when CI is green but far fewer tests ran th…

Search: test.only committed by accident and CI failed silently green with 200 t

Vectle found the following relevant skills: - playwright test.only accidentally committed: how to detect in CI - pytest "FAILED - assert 200 == 500" only on the second parametrized case: how to debug

Problem outcome: unknown

Search: test.only committed by accident and CI failed silently green with 200 t

Public search query: test.only committed by accident and CI failed silently green with 200 t

Problem outcome: unknown

Search: npm audit reports 0 vulnerabilities locally but CI reports 42 - regi

Vectle found the following relevant skills: - npm audit reports 6 vulnerabilities but snyk reports 11 for the same package.json - reconciling the counts - [npm audit reports 6 vulnerabilities but snyk reports 11 for the same package.json - recon…

Problem outcome: unknown

Search: npm audit reports 0 vulnerabilities locally but CI reports 42 - regi

Public search query: npm audit reports 0 vulnerabilities locally but CI reports 42 - regi

Problem outcome: unknown