stablyai/agent-skills/github-actions-setup
Claude Code and agent skill by stablyai/agent-skills
- community
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-setupSKILL.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
- Work autonomously - Detect the project setup and generate the workflow without unnecessary questions
- Ask permission only for:
- Writing the workflow file
- Enabling optional features (self-healing, scheduled runs)
- Show what you're doing - Announce each step as you begin it
- 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:
Detect the following automatically:
1a. Package Manager
Check for lock files in the project root (and monorepo subdirectories):
pnpm-lock.yaml-> pnpmyarn.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
packageManagerfield inpackage.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 requirescorepack enable, classic does not
1c. Node.js Version
Check for version hints:
.nvmrcor.node-versionfileengines.nodeinpackage.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
testDirsetting 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
workspacesin rootpackage.json,pnpm-workspace.yaml, orlerna.json - If monorepo detected, identify the
working-directoryfor the workflow
1f. Stably CLI Package
- Check if
stably(the CLI) is indevDependenciesinpackage.json - This is separate from
@stablyai/playwright-test(the SDK) — the SDK does NOT include the CLI - If
stablyis missing, flag it — the workflow will fail withstably: 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:
Step 2: Choose Workflow Features
Ask the user:
WAIT for user's choice. If they just say "yes" or "go ahead", use Basic.
Step 3: Generate Workflow File
Announce:
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:
- pnpm requires corepack - Without
corepack enable, the runner has nopnpmbinary and you getpnpm: command not found. Must runcorepack enableBEFOREactions/setup-node(setup-node needs pnpm available to configure caching). - yarn (berry/v2+) requires corepack - Same as pnpm. For yarn classic (v1), it's pre-installed on GitHub runners.
- Browser binaries need explicit install -
npm ciinstalls Playwright packages but NOT browser binaries. Must runstably install --with-deps chromiumas a separate step.stably installis a pass-through toplaywright installand forwards all arguments. - `--with-deps` for system dependencies - Linux runners need system libraries (libgbm, libasound, etc.). The
--with-depsflag installs them. Without it, browser launch fails with missing library errors. Specifyingchromium(instead of all browsers) speeds up the install. - 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-levelenv:to avoid forgetting. - Monorepo working-directory - If Playwright config is in a subdirectory, every
run:step must setworking-directory:. - `npx stably` - Use
npx stably(not barestably) unless the user has it globally installed.npxresolves from the project's localnode_modules. - `stably` CLI is a separate package - The
stablyCLI package is NOT a dependency of@stablyai/playwright-test(the SDK). Users must havestablyin theirdevDependenciesfornpx stablyto work. If it's missing, the skill should add it. Checkpackage.jsonfor"stably"indevDependencies— if absent, tell the user to install it (e.g.,npm install -D stably).
Template: npm
Template: pnpm
Template: yarn berry (v2+)
Note: Yarn berry (v2+) resolves local bin entries viayarn <bin>, soyarn stablyworks directly.This does NOT work in yarn classic — see the classic template below.
Template: yarn classic (v1)
Note: Yarn classic (v1) is pre-installed on GitHub runners — nocorepack enableneeded.Usenpx stablyinstead ofyarn stablysince 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:
And adjust the cache-dependency-path so setup-node finds the lockfile:
Note:defaults.run.working-directoryonly applies torun:steps, notuses:steps likeactions/checkoutoractions/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:
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
- SKILL.md in the repositoryCheckingskills/github-actions-setup/SKILL.md
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
[](https://verified-skill.com/skills/stablyai/agent-skills/github-actions-setup)