gathering-context
Context Gatherer
Reads all available artifacts for a failing WebdriverIO test and returns a structured markdown summary. Called by the Investigator agent — does not diagnose or fix, only gathers and organizes evidence.
Inputs
The Investigator passes a structured failure object:
- testName: string # The it() / describe() title
- specFile: string # Relative path to the spec file
- errorMessage: string # The assertion or exception message
- stackTrace: string # Full stack trace
- logFile?: string # Optional: path to wdio log file
- snapshotDir?: string # Optional: dir where HTML/screenshots/video are saved
Project Context Files
More from klamping/webdriverio-skills
writing-webdriverio-code
Use when implementing, extending, or fixing WebdriverIO tests, including converting pseudo-code scaffolds into clean WDIO commands, selectors, waits, and assertions.
21analyze-website
Use when investigating and documenting website structure, components, functionality importance, and version-to-version differences for human understanding and test planning.
14running-webdriverio-tests
Run WebdriverIO test files from the command line. Use when debugging tests, gathering context about test behavior, or verifying changes resolved an issue.
13creating-test-structure
Use when creating or extending WebdriverIO test structure from a markdown test plan by adding describe/it/hooks and pseudo-code comments without implementing WDIO commands yet.
10skipped-test-manager
Use when temporarily skipping failing WebdriverIO tests for app bugs or unimplemented functionality, while tracking ownership, ticket linkage, and re-enable status.
9managing-project-customizations
Use when initializing or refreshing project-specific WebdriverIO context so other skills can reuse cached configuration, conventions, and environment details with lower token and execution cost.
9