claudeskills.page

16 skills · 10 categories

Claude Code skills for GitHub Actions

GitHub Actions skills for faster pipelines, caching, matrix builds, OIDC deploys, reusable workflows and running Claude Code headless in CI for reviews and triage.

Install all 16 Browse the list

Start with these

  1. 1

    GitHub Actions

    Faster CI, read-only tokens, zero stored cloud keys

    Claude rewrites workflows so irrelevant changes skip CI, superseded runs cancel, and package and Docker caches make the warm path fast. Tokens default to read-only, deploys use OIDC with subject-restricted trust policies and protected environments, and untrusted PR text never reaches a shell. Results are linted with actionlint and zizmor and reported with before-and-after timings.

  2. 2

    Playwright E2E

    End-to-end tests that never need a sleep

    Claude writes Playwright tests the way the Playwright team recommends: role and label locators, auto-retrying assertions, API-seeded fixtures with teardown, and one login reused through storageState. When a test fails it reads the trace before touching code, and it ships CI config that shards runs, merges blob reports, and keeps traces for every failure.

  3. 3

    Lighthouse CI

    Fail the PR when pages get slower, not later

    Claude adds Lighthouse CI that teams keep enabled: it baselines key pages over several runs, asserts on LCP, TBT, CLS and byte weight using median aggregation instead of a volatile score, wires autorun into GitHub Actions or GitLab after the production build, and controls noise from shared runners and third-party scripts. Thresholds start at today's numbers and tighten after each win.

All 16 GitHub Actions skills

Grouped by category. Each card opens the full playbook, example prompts and install commands.

Claude Code Mastery 1

No. 007

Headless CI Agent

Claude in your pipeline, bounded and injection-aware

Sets up Claude Code to run unattended in scripts and CI without hanging, overspending, or obeying instructions hidden in a pull request. Claude splits privileges so the agent only reads and writes workspace files while plain workflow steps hold tokens, commits the prompt as a reviewed file, validates the JSON result with jq, caps turns and time, and tests the job against an injection fixture.

headless-ci-agent 196 lines

Engineering Workflow 4

No. 034

Issue Triage

Every issue leaves triage with one clear state

Claude runs each issue through a fixed decision flow: actionable here, duplicate, enough information, reproducible, then type, severity, area and owner. Duplicates are found by error text rather than titles, missing-info requests name the exact facts needed, reproduction is time-boxed, and bulk label and close changes are shown as a table for confirmation before anything is applied.

issue-triage 188 lines
No. 038

Pull Request Writer

PRs a reviewer can approve in one sitting

Claude reads the real three-dot diff before writing, then produces a PR title that works as a squash commit and a description covering motivation, a suggested review order, test commands it actually ran, screenshots for UI, and risk, rollout and rollback notes. Oversized branches get split or stacked along clean seams, with gh CLI commands to create and update each PR.

pull-request-writer 185 lines
★ No. 026

Code Review

Findings ranked by severity, minus the nitpicks

Gives Claude a two-pass review method for teammates' diffs: first design and correctness traced with concrete adversarial inputs, then a sweep for auth gaps, injection, races, unsafe migrations, N+1 queries, and weak tests. Findings are verified before posting, labeled blocker through nit, carry a file and line plus a fix, and end with a verdict that states what was not reviewed.

code-review 204 lines · 2 files
No. 041

Review Feedback Resolution

Every review thread closed with a commit or a reason

Claude pulls every unresolved review thread through the GitHub GraphQL API and turns it into a checklist, reads all feedback before editing, and classifies each item as blocking, question, suggestion, nit or out of scope. Fixes land in focused commits with tests, each thread gets a reply with a commit SHA or evidence, settled threads are resolved, and the reviewer receives one summary with a re-request.

review-feedback-resolution 154 lines · 2 files

Testing 3

★ No. 137

Playwright E2E

End-to-end tests that never need a sleep

Claude writes Playwright tests the way the Playwright team recommends: role and label locators, auto-retrying assertions, API-seeded fixtures with teardown, and one login reused through storageState. When a test fails it reads the trace before touching code, and it ships CI config that shards runs, merges blob reports, and keeps traces for every failure.

playwright-e2e 220 lines · 2 files
No. 129

Cypress E2E

Cypress tests that wait on aliases, never on timers

Claude writes Cypress specs that respect the command queue: stable data-cy or role selectors, retrying should assertions, intercept aliases instead of fixed waits, and cy.session logins with validation so each spec logs in once through the API. It seeds data with cy.task, adds component tests with cy.mount, and parallelizes CI through Cypress Cloud or free spec splitting.

cypress-e2e 260 lines
No. 141

Testcontainers

Real databases in tests, started once and reset fast

Claude replaces database mocks and H2 stand-ins with the production engine in a container, started once per run rather than per test. It runs the real migrations, picks rollback, truncation, template databases or snapshots for isolation, gives each parallel worker its own database, and sets up GitHub Actions or GitLab Docker-in-Docker so the suite passes cold, shuffled and in parallel.

testcontainers 202 lines · 2 files

DevOps & SRE 2

★ No. 154

GitHub Actions

Faster CI, read-only tokens, zero stored cloud keys

Claude rewrites workflows so irrelevant changes skip CI, superseded runs cancel, and package and Docker caches make the warm path fast. Tokens default to read-only, deploys use OIDC with subject-restricted trust policies and protected environments, and untrusted PR text never reaches a shell. Results are linted with actionlint and zizmor and reported with before-and-after timings.

github-actions 227 lines · 2 files
No. 150

CI Pipeline Speed

Shorten the critical path, prove it with medians

Claude baselines several recent runs with a bundled analyzer that finds the critical path, queue delay and slowest steps, then works on that path only: removing duplicate work, adding correctly keyed caches, sharding tests by timing data, and running affected-only builds in monorepos. Results are reported as before-and-after medians with test counts unchanged.

ci-pipeline-speed 171 lines · 2 files

Cloud Platforms 1

★ No. 174

AWS IAM Least Privilege

Exact permissions, and AccessDenied solved by evidence

Claude maps each API call to the exact IAM actions, ARNs and condition keys it needs instead of reaching for wildcards. AccessDenied errors are traced through caller identity, CloudTrail, decoded messages and the evaluation order to the policy type that denied. Policies are validated with Access Analyzer and a bundled stdlib linter that flags PassRole, escalation paths and open OIDC trusts.

aws-iam 204 lines · 2 files

Performance 1

★ No. 300

Lighthouse CI

Fail the PR when pages get slower, not later

Claude adds Lighthouse CI that teams keep enabled: it baselines key pages over several runs, asserts on LCP, TBT, CLS and byte weight using median aggregation instead of a volatile score, wires autorun into GitHub Actions or GitLab after the production build, and controls noise from shared runners and third-party scripts. Thresholds start at today's numbers and tighten after each win.

lighthouse-ci 173 lines · 2 files

Mobile 1

No. 333

Fastlane CI

One command from commit to TestFlight and Play

Claude turns laptop releases into reproducible fastlane lanes: Gemfile-pinned fastlane, match certificates fetched read-only behind setup_ci, App Store Connect API keys instead of Apple ID sessions, build numbers derived from the store, and Play uploads that land on internal and promote with a staged rollout. A bundled checker flags committed secrets and risky lanes before CI runs them.

fastlane-ci 230 lines · 2 files

Documents & Files 1

No. 380

Report Automation

Recurring reports that refuse to send bad numbers

Claude turns a hand-built weekly or monthly report into one command keyed on the reporting period: versioned SQL, validation gates for freshness, completeness and reconciliation, deterministic matplotlib charts, and Jinja2 templates rendered to PDF, HTML email or Slack. Runs are idempotent, never resend by accident, print their template version, and leave a manifest for audit.

report-automation 218 lines

Integrations 1

No. 406

GitHub API Automation

Bulk GitHub changes with dry runs and throttling

Claude scripts GitHub the careful way: it picks the least-privileged credential (GITHUB_TOKEN, fine-grained PAT, or GitHub App), prototypes with gh api, paginates every list, throttles writes under primary and secondary limits, and runs a dry run you approve before mutating anything. App webhooks are verified against the raw body and deduped by delivery ID.

github-api-automation 215 lines · 2 files

Automation & Tooling 1

★ No. 501

Scheduled Jobs

Cron jobs safe to rerun, overlap-proof and watched

Claude designs the job to be rerun safely before choosing a schedule, then wires it into a systemd timer, cron, launchd or a Kubernetes CronJob with catch-up, jitter and a time limit. A bundled wrapper adds a portable single-instance lock, UTC logs and healthcheck pings, and every job ships with a heartbeat monitor that alerts when it silently stops running.

scheduled-jobs 212 lines · 2 files

Install

Every GitHub Actions skill in one command

Installs into ~/.claude/skills/. Add --project after -- to install into the current repository.

curl -fsSL https://claudeskills.page/install.sh | sh -s -- github-actions playwright-e2e lighthouse-ci headless-ci-agent issue-triage pull-request-writer cypress-e2e fastlane-ci code-review review-feedback-resolution aws-iam scheduled-jobs testcontainers ci-pipeline-speed report-automation github-api-automation

GitHub Actions skills FAQ

What is the best Claude Code skill for GitHub Actions?

Start with GitHub Actions: Faster CI, read-only tokens, zero stored cloud keys. Then add Playwright E2E and Lighthouse CI, which cover the next most common GitHub Actions requests.

How do I install all 16 GitHub Actions skills at once?

Pass every name to the installer in one command: curl -fsSL https://claudeskills.page/install.sh | sh -s -- github-actions playwright-e2e lighthouse-ci headless-ci-agent issue-triage pull-request-writer cypress-e2e fastlane-ci code-review review-feedback-resolution aws-iam scheduled-jobs testcontainers ci-pipeline-speed report-automation github-api-automation. Add --project to install them into the current repository's .claude/skills/ folder so your team gets them too.

Do these GitHub Actions skills work outside Claude Code?

Yes. Each skill uses only the portable Agent Skills frontmatter, so the same folder works on claude.ai, through the Claude API and in the Agent SDK. Skills that run bundled scripts need an environment with code execution.

Related technologies

esc