Loading...
Loading...
Found 9 Skills
Analyze a completed Meticulous test run — fetch the diff summary, inspect representative screenshots, DOM diffs, and timelines. Accepts a test-run ID, a PR number (resolved against the local repo), or otherwise identifies the test-run ID from the local repo's current branch and its associated PR. Use when asked to review Meticulous test results, or while reviewing or babysitting a PR to assess and fix a failing Meticulous Tests CI check.
Work with Shiplight Cloud v2/Nova test results APIs: create local or CI test runs, upload result artifacts, complete runs, and retrieve signed artifact URLs.
Run /check-quality, then fix the highest priority quality issue. Creates one fix per invocation. Invoke again for next issue. Use /log-quality-issues to create issues without fixing.
Comprehensive Bun runtime expertise covering all major features. Use when working with Bun projects, migrating from Node.js, or leveraging Bun-specific APIs. Activates for: Bun.serve, Bun.file, bun:test, bun:sqlite, bun install, bun build, bunfig.toml, TypeScript in Bun, package manager operations, bundler configuration, and Node.js compatibility questions.
Bun JavaScript/TypeScript runtime and all-in-one toolkit. Covers runtime, package manager, bundler, test runner, HTTP server, WebSockets, SQLite, S3, Redis, file I/O, shell scripting, FFI, Markdown parser. Keywords: bun, bunx, bun install, bun run, bun test, bun build, Bun.serve, Bun.file, bun:sqlite, Bun.markdown.
Combined command for OpenHarmony XTS compilation and execution. Complete the compilation and execution of XTS test projects in one stop. Use this Skill when you need to execute the full XTS test process: (1) Compile the XTS test project to generate HAP files, (2) Run the XTS test and display the results. Supports passing --package and --api parameters to the execution phase.
Node.js server-side JavaScript runtime with npm ecosystem. Use for backend development.
Search across all timelines in an Antithesis test run to find events, correlate property failures, and answer temporal questions about ordering and causation (e.g., did event A always precede failure B? do failures occur even without a preceding fault?).
Update dependencies safely — check changelogs, run tests, create PR