github-actions-ci
Skill4 starsChanged 27 days agoMITView on GitHub
Use when setting up CI/CD with GitHub Actions, writing or fixing a workflow YAML, running tests or lint on pull requests, caching dependencies, deploying on push, or debugging a failing or slow GitHub Actions run.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- AndrewBrown-USDA/aigb-skills-usdatheir own version, first seen Oct 31, 2026
- wsoule/dispatchtheir own version, first seen Oct 13, 2026
- gregwebs/skills-sdlctheir own version, first seen Sep 29, 2026
- cvsz/zomegatheir own version, first seen Sep 2, 2026
- techdeveloper-org/mcp-jenkins-citheir own version, first seen Aug 12, 2026
- THEROCKSSS/hermes-skills-portfoliotheir own version, first seen Aug 3, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- gregwebs/skills-sdlc★ 20same name
- AndrewBrown-USDA/aigb-skills-usda★ 7same name
- wsoule/dispatch★ 2same name
- cvsz/zomega★ 1same name
- MaheshAwasare/claude-skills-pro★ 1same name
- minagayid/Agents★ 1same name
- THEROCKSSS/hermes-skills-portfolio★ 1same name
- techdeveloper-org/mcp-jenkins-ci★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository30 other files it gives its agents.
- accessibility-auditSkill
- api-design-reviewSkill
- api-test-writerSkill
- architecture-diagramSkill
- bug-debuggerSkill
- bug-report-writerSkill
- changelog-writerSkill
- codebase-onboardingSkill
- code-reviewSkill
- database-schema-designSkill
- dependency-upgradeSkill
- design-handoff-specSkill
- design-reviewSkill
- dockerize-appSkill
- figma-design-compareSkill
- flaky-test-fixerSkill
- git-commit-writerSkill
- playwright-e2e-testsSkill
- prd-writerSkill
- proof-of-done-liteSkill
- readme-writerSkill
- refactor-plannerSkill
- security-auditSkill
- seo-auditSkill
- test-case-generatorSkill
- test-plan-writerSkill
- test-writerSkill
- ux-research-synthesisSkill
- ux-writingSkill
- web-performance-auditSkill
The file
Files
GitHub Actions CI
Overview
A good pipeline runs the same checks a developer runs locally, fails fast with a clear message, and finishes in minutes. Build it from the project's real commands and keep it secure by default.
Method
- Discover the checks the project already has: install, lint, typecheck, test, build commands from
package.json,Makefile,pyproject.toml,pom.xml,go.mod. Note runtime versions and services the tests need (Postgres, Redis). - Write
.github/workflows/ci.ymlfrom the template below. Add a deploy workflow only if asked, and only onmainafter CI passes. - Validate with
actionlintif available. Push to a branch and watch the run:gh run watch. - Debugging a failing run:
gh run view <id> --log-failed, reproduce the failing command locally with the same runtime version, compare environment variables and service versions.
Template
name: CI
on:
pull_request:
push:
branches: [main]
permissions:
contents: read
concurrency:
group: ci-${{ github.ref }}
cancel-in-progress: true
jobs:
check:
runs-on: ubuntu-latest
timeout-minutes: 15
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version-file: .nvmrc
cache: npm
- run: npm ci
- run: npm run lint
- run: npm run typecheck
- run: npm test
- run: npm run buildFor other stacks swap the setup step: actions/setup-python@v5 (cache: pip), actions/setup-java@v4 (cache: maven), actions/setup-go@v5 (cache built in).
Services for integration tests:
services:
postgres:
image: postgres:16
env: { POSTGRES_PASSWORD: postgres }
ports: ["5432:5432"]
options: >-
--health-cmd pg_isready --health-interval 5s --health-retries 10Rules
| Rule | Why |
Least privilege: top-level permissions: contents: read, widen per job only | Limits damage from a compromised step |
Secrets via ${{ secrets.X }} only, never echoed; no secrets on pull_request from forks | Prevents leaks |
Pin third-party actions to a full commit SHA; official actions/* to a major version | Supply-chain safety |
| Cache dependencies through the setup action | Faster runs |
concurrency with cancel-in-progress | No queue of outdated runs |
timeout-minutes on every job | Hung jobs do not burn minutes |
| Matrix only where it matters (supported runtime versions, OSes) | Each entry costs time |
Common mistakes
- CI runs commands that do not exist locally, so failures cannot be reproduced.
- Using
npm installinstead ofnpm ci. pull_request_targetwith checkout of the PR code: gives untrusted code access to secrets.- Deploying from a workflow that does not depend on tests passing.
- Hiding failures with
continue-on-error: trueor|| true.
Made by Wageesha Tripathi · LinkedIn · Email · More skills
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

