Menu
Analyze Playwright test logs on Buildkite to extract failed-only tests across jobs.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | buildkite-playwright-failures |
| description | Analyze Playwright test logs on Buildkite to extract failed-only tests across jobs. |
Use this skill when you need a compact, human-readable overview of failing Playwright tests from Buildkite job logs.
This workflow uses the bkci CLI. Run /skill:buildkite-cli first if bkci is not set up yet.
./scripts/extract-playwright-failures.cjs --org ORG --pipeline PIPELINE --build BUILD_NUMBER
Options:
--bkci-path PATH (default: bkci or $BKCI_BIN)--error-for TEST_NAME (fetch error details for a single test)--job-id ID (required with --error-for)--job-url URL (optional with --error-for)--failed-line-row N (optional with --error-for)The script always emits JSON and caches summary results under your temp dir ($TMPDIR/pi-buildkite-playwright-failures). It refreshes the cache if any Playwright job state changes.
Summary output includes:
summaryjobs[] entries with:
jobName, jobId, jobUrl, label, statefailedLine, failedLineRowtests (string list)testEntries (objects with name + row)errorError lookup output (--error-for) includes:
error.testName, error.jobId, error.jobUrlerror.matchRow, error.startRow, error.endRowerror.lines (array of log lines)meta.checkedAtWhen presenting results to a human, format the summary with:
all)bkci --raw builds get.bkci jobs log get.X failed summary section and extracts failed test lines.bkci --raw builds get --org ORG --pipeline PIPELINE --build BUILD_NUMBER
Find failed Playwright jobs from data.jobs[].
Fetch a job log:
bkci jobs log get --org ORG --pipeline PIPELINE --build BUILD_NUMBER --job JOB_ID
X failed section.bkci jobs log get returns cleaned logs (ANSI/control sequences stripped) in normalized mode.bkci auth setup manually.Structured workflow for investigating public software supply-chain attacks across local repositories, GitHub organizations, and CI/host fleets. Use when asked to assess exposure to compromised packages, malicious releases, package-manager attacks, GitHub Actions/OIDC abuse, or published IOC lists.
Multi-model code review. Runs code-review skill with 2 models in parallel, then synthesizes findings.
Multi-agent workflow (tracer/resolver/bypass) for secure code review, exploitability triage, and PoC validation in codebases. Use when conducting structured security research or penetration test analysis.
Send a desktop notification when pi finishes a task. Works on macOS, Windows, and Linux. On first use, interactively asks the user to choose a notification preference (always, ask every time, or never) via arrow-key selector. Use this skill at the end of every task completion — after committing, after finishing a code change, after answering a question, or any other unit of work.
Search a specific GitHub repository for code using gh search and fetch file contents via gh api without cloning. Use when given a repo URL and query to locate logic in remote repos.
Use the bkci CLI to query Buildkite builds, logs, artifacts, and token scope status with LLM-friendly JSON output.