ci-cd-testing-specialist

Automate GitHub Actions CI/CD test execution and PR reporting for Node web apps.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Whaleylaw/llm-lawyer --skill ci-cd-testing-specialist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-cd-testing-specialist
Source: https://github.com/Whaleylaw/llm-lawyer/tree/main/.claude/skills/ci-cd-testing-specialist
Command: npx skills add https://github.com/Whaleylaw/llm-lawyer --skill ci-cd-testing-specialist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves unreliable or missing automated tests in CI/CD by providing prescriptive workflows, configuration patterns, and operational checklists to run unit and E2E tests, publish coverage, and surface test failures on every commit and pull request.

Core Features & Use Cases

  • GitHub Actions Workflows: Ready-made patterns for running linting, type checks, unit tests, and E2E suites on pushes and PRs.
  • E2E & Service Setup: Guidance for running Playwright tests with service containers (Postgres), installing browsers, and waiting for app readiness.
  • Coverage & Reporting: Integrations for generating coverage reports, uploading to Codecov, enforcing thresholds, and publishing test results in PRs.
  • Performance & Reliability: Strategies for caching dependencies, parallelizing jobs, sharding tests, retrying flaky tests, and uploading artifacts on failure.
  • Use Case: Configure CI for a Node/React legal case management app to run Vitest unit tests and Playwright E2E on PRs, upload coverage to Codecov, and block merges when checks fail.

Quick Start

Create a GitHub Actions workflow that runs lint, type checks, Vitest unit tests, Playwright E2E tests, caches dependencies, uploads coverage to Codecov, and fails the PR if coverage is below 80%.

Frequently Asked Questions about ci-cd-testing-specialist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run Playwright E2E tests in GitHub Actions with service containers?

Running Playwright E2E tests in GitHub Actions requires orchestrating service containers like Postgres, installing browsers, and configuring jobs to wait for application readiness before executing the test suite.

How do I upload Vitest coverage to Codecov and block PRs below the threshold?

Uploading Vitest coverage to Codecov involves generating a coverage report, uploading it via the Codecov action, and configuring your GitHub Actions workflow to fail the pull request if coverage falls below 80%.

How to handle flaky tests and parallelize E2E test runs in CI pipelines?

Handling flaky E2E tests in CI pipelines involves sharding tests across parallel jobs, configuring retry strategies for flaky tests, and uploading artifacts on failure to capture diagnostic output.

Do I need to configure pipeline caching for Node-based web applications in CI?

Configuring pipeline caching for Node-based web applications is necessary to optimize CI execution speed by storing dependencies, which reduces installation times across repeated workflow runs.

What is the best way to report test results on pull requests in GitHub Actions?

Reporting test results on pull requests in GitHub Actions involves capturing unit and E2E test outputs, enforcing coverage thresholds, and surfacing check failures to block merges automatically.