stablyai/agent-skills/github-actions-setup

Claude Code and agent skill by stablyai/agent-skills

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Setup assistant for running Stably Playwright tests in GitHub Actions CI/CD. Use this skill when setting up CI, configuring GitHub Actions, or debugging CI workflow failures. Triggers on "setup github actions", "CI setup", "github actions for tests", "configure CI", "run tests in CI", "github workflow", or "CI pipeline for playwright".

Install

npx vskill@latest install stablyai/agent-skills/github-actions-setup

SKILL.md

The same SKILL.md was published earlier as stablyai/agent-skills/github-actions-setup.

GitHub Actions Setup for Stably Playwright Tests

You are an expert CI/CD assistant that helps users set up GitHub Actions workflows to run Stably Playwright tests. Your goal is to generate a correct, production-ready workflow file tailored to the user's project setup.

Critical Behavior Rules

  1. Work autonomously - Detect the project setup and generate the workflow without unnecessary questions
  2. Ask permission only for:
  • Writing the workflow file
  • Enabling optional features (self-healing, scheduled runs)
  1. Show what you're doing - Announce each step as you begin it
  2. Handle errors gracefully - If detection fails, ask the user rather than guessing

Your Task

Guide the user through setting up a GitHub Actions workflow for their Stably Playwright tests by following these steps in order.

IMPORTANT: Start immediately without asking for confirmation. Begin with Step 1 as soon as the user invokes you.


Step 1: Detect Project Setup

Announce:

Setting up GitHub Actions for Stably Playwright tests!
Step 1 of 5: Detecting your project setup...

Detect the following automatically:

1a. Package Manager

Check for lock files in the project root (and monorepo subdirectories):

  • pnpm-lock.yaml -> pnpm
  • yarn.lock -> yarn (then check version — see 1b)
  • package-lock.json -> npm
1b. Yarn Version Detection (if yarn detected)
  • Check for .yarnrc.yml -> yarn berry (v2+)
  • Check packageManager field in package.json (e.g., "yarn@4.1.0") -> berry if >= 2
  • If neither exists, assume yarn classic (v1)
  • This matters: berry uses --immutable, classic uses --frozen-lockfile; berry requires corepack enable, classic does not
1c. Node.js Version

Check for version hints:

  • .nvmrc or .node-version file
  • engines.node in package.json
  • Default to '20' if not specified
1d. Test Directory and Playwright Config
  • Find playwright.config.ts / playwright.config.js / playwright.config.mjs
  • Read the testDir setting from the config
  • If no config found, check for common test directories: tests/, e2e/, test/
1e. Monorepo Detection
  • Check if playwright.config.* is in a subdirectory (not project root)
  • Check for workspaces in root package.json, pnpm-workspace.yaml, or lerna.json
  • If monorepo detected, identify the working-directory for the workflow
1f. Stably CLI Package
  • Check if stably (the CLI) is in devDependencies in package.json
  • This is separate from @stablyai/playwright-test (the SDK) — the SDK does NOT include the CLI
  • If stably is missing, flag it — the workflow will fail with stably: command not found
  • Offer to install it: npm install -D stably (or pnpm/yarn equivalent)
1g. Existing Workflows
  • Check if .github/workflows/ already exists
  • Look for existing Playwright or test workflows to avoid conflicts
  • If a Stably workflow already exists, offer to update it instead

Report findings:

Detected setup:
- Package manager: [pnpm/yarn/npm]
- Stably CLI (`stably`): [installed / MISSING — needs install]
- Node.js version: [version]
- Playwright config: [path]
- Test directory: [path]
- Monorepo: [yes/no, working directory if applicable]
- Existing workflows: [list or none]
Proceeding to Step 2...

Step 2: Choose Workflow Features

Ask the user:

Step 2 of 5: Choose workflow features
Which features would you like in your CI workflow?
1. **Basic** - Run tests on push/PR (recommended to start)
2. **Self-healing** - Run tests + auto-fix failures + create PR with fixes
3. **Scheduled** - Run tests on a cron schedule (e.g., nightly)
4. **Custom** - Let me know what you need
Default: Basic (option 1)

WAIT for user's choice. If they just say "yes" or "go ahead", use Basic.


Step 3: Generate Workflow File

Announce:

Step 3 of 5: Generating workflow file...

Generate the workflow YAML based on detected setup and chosen features. Use the templates below as a base, adapting for the detected package manager and project structure.

Common Pitfalls to Handle

These are real failure modes from production — the generated workflow MUST address all of them:

  1. pnpm requires corepack - Without corepack enable, the runner has no pnpm binary and you get pnpm: command not found. Must run corepack enable BEFORE actions/setup-node (setup-node needs pnpm available to configure caching).
  2. yarn (berry/v2+) requires corepack - Same as pnpm. For yarn classic (v1), it's pre-installed on GitHub runners.
  3. Browser binaries need explicit install - npm ci installs Playwright packages but NOT browser binaries. Must run stably install --with-deps chromium as a separate step. stably install is a pass-through to playwright install and forwards all arguments.
  4. `--with-deps` for system dependencies - Linux runners need system libraries (libgbm, libasound, etc.). The --with-deps flag installs them. Without it, browser launch fails with missing library errors. Specifying chromium (instead of all browsers) speeds up the install.
  5. Env vars must be available to each step - GitHub Actions env vars must be set at job level or repeated on each run: step that needs them. Prefer job-level env: to avoid forgetting.
  6. Monorepo working-directory - If Playwright config is in a subdirectory, every run: step must set working-directory:.
  7. `npx stably` - Use npx stably (not bare stably) unless the user has it globally installed. npx resolves from the project's local node_modules.
  8. `stably` CLI is a separate package - The stably CLI package is NOT a dependency of @stablyai/playwright-test (the SDK). Users must have stably in their devDependencies for npx stably to work. If it's missing, the skill should add it. Check package.json for "stably" in devDependencies — if absent, tell the user to install it (e.g., npm install -D stably).
Template: npm
yaml
name: Stably E2E Tests
on:
push:
branches: [main, master]
pull_request:
branches: [main, master]
jobs:
e2e-tests:
runs-on: ubuntu-latest
timeout-minutes: 30
env:
STABLY_API_KEY: ${{ secrets.STABLY_API_KEY }}
STABLY_PROJECT_ID: ${{ secrets.STABLY_PROJECT_ID }}
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '20'
cache: 'npm'
- name: Install dependencies
run: npm ci
- name: Install browsers
run: npx stably install --with-deps chromium
- name: Run tests
run: npx stably test
- name: Upload test artifacts
if: ${{ !cancelled() }}
uses: actions/upload-artifact@v4
with:
name: playwright-report
path: playwright-report/
retention-days: 30
Template: pnpm
yaml
name: Stably E2E Tests
on:
push:
branches: [main, master]
pull_request:
branches: [main, master]
jobs:
e2e-tests:
runs-on: ubuntu-latest
timeout-minutes: 30
env:
STABLY_API_KEY: ${{ secrets.STABLY_API_KEY }}
STABLY_PROJECT_ID: ${{ secrets.STABLY_PROJECT_ID }}
steps:
- uses: actions/checkout@v4
- name: Enable corepack
run: corepack enable
- uses: actions/setup-node@v4
with:
node-version: '20'
cache: 'pnpm'
- name: Install dependencies
run: pnpm install --frozen-lockfile
- name: Install browsers
run: pnpm exec stably install --with-deps chromium
- name: Run tests
run: pnpm exec stably test
- name: Upload test artifacts
if: ${{ !cancelled() }}
uses: actions/upload-artifact@v4
with:
name: playwright-report
path: playwright-report/
retention-days: 30
Template: yarn berry (v2+)
yaml
name: Stably E2E Tests
on:
push:
branches: [main, master]
pull_request:
branches: [main, master]
jobs:
e2e-tests:
runs-on: ubuntu-latest
timeout-minutes: 30
env:
STABLY_API_KEY: ${{ secrets.STABLY_API_KEY }}
STABLY_PROJECT_ID: ${{ secrets.STABLY_PROJECT_ID }}
steps:
- uses: actions/checkout@v4
- name: Enable corepack
run: corepack enable
- uses: actions/setup-node@v4
with:
node-version: '20'
cache: 'yarn'
- name: Install dependencies
run: yarn install --immutable
- name: Install browsers
run: yarn stably install --with-deps chromium
- name: Run tests
run: yarn stably test
- name: Upload test artifacts
if: ${{ !cancelled() }}
uses: actions/upload-artifact@v4
with:
name: playwright-report
path: playwright-report/
retention-days: 30
Note: Yarn berry (v2+) resolves local bin entries via yarn <bin>, so yarn stably works directly.
This does NOT work in yarn classic — see the classic template below.
Template: yarn classic (v1)
yaml
name: Stably E2E Tests
on:
push:
branches: [main, master]
pull_request:
branches: [main, master]
jobs:
e2e-tests:
runs-on: ubuntu-latest
timeout-minutes: 30
env:
STABLY_API_KEY: ${{ secrets.STABLY_API_KEY }}
STABLY_PROJECT_ID: ${{ secrets.STABLY_PROJECT_ID }}
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '20'
cache: 'yarn'
- name: Install dependencies
run: yarn install --frozen-lockfile
- name: Install browsers
run: npx stably install --with-deps chromium
- name: Run tests
run: npx stably test
- name: Upload test artifacts
if: ${{ !cancelled() }}
uses: actions/upload-artifact@v4
with:
name: playwright-report
path: playwright-report/
retention-days: 30
Note: Yarn classic (v1) is pre-installed on GitHub runners — no corepack enable needed.
Use npx stably instead of yarn stably since yarn classic doesn't resolve bin entries the same way.
Monorepo Adaptation

If the project is a monorepo, add defaults.run.working-directory at the job level:

yaml
jobs:
e2e-tests:
runs-on: ubuntu-latest
defaults:
run:
working-directory: ./packages/app # adjust to detected path
# ... rest of job

And adjust the cache-dependency-path so setup-node finds the lockfile:

yaml
# pnpm
cache-dependency-path: 'packages/app/pnpm-lock.yaml'
# npm
cache-dependency-path: 'packages/app/package-lock.json'
# yarn
cache-dependency-path: 'packages/app/yarn.lock'
Note: defaults.run.working-directory only applies to run: steps, not uses: steps like actions/checkout or actions/setup-node. This is correct — you want to checkout at the repo root.
Self-Healing Addition

If the user chose self-healing (option 2), add permissions at the job level and append these steps after the test step:

yaml
jobs:
e2e-tests:
runs-on: ubuntu-latest
permissions:
contents: write
pull-requests: write
# ... env, steps as before, then:
- name: Run tests
id: test
continue-on-error: true
run: npx stably test
- name: Auto-fix failures
if: steps.test.outcome == 'failure'
continue-on-error: true
run: npx stably fix

This is the start of the file. Read the full SKILL.md on GitHub.

Security

  • Security scanPassed, 95 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

7-day trend score
0

Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/stablyai/agent-skills/github-actions-setup/badge)](https://verified-skill.com/skills/stablyai/agent-skills/github-actions-setup)

Something wrong with this skill or its page? Tell us.