Skip to content
Skills Library
DevOps & cloud · Automation

setup-ci

/setup-ci

Set up CI that runs the full test suite on every merge or pull request - on GitLab or GitHub, on hosted runners or your own machine - with the JUnit report eng-kit reads, cancel-on-new-push, a test database in RAM and a nightly random-order run. Use when the person asks to set up CI, a runner, a self-hosted runner, or to make tests run automatically on merge requests.

Repository
eng-kit ↗
Licence
MIT
Last repository change
04.11.2026

Assessment and security

86/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content21 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
4
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 04.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Set up CI that runs the full test suite on every merge or pull request - on GitLab or GitHub, on hosted runners or your own machine - with the JUnit report eng-kit reads, cancel-on-new-push, a test database in RAM and a nightly random-order run. Use when the person asks to set up CI, a runner, a self-hosted runner, or to make tests run automatically on merge requests.

Arguments

/setup-ci [gitlab | github]
Original author description

Set up CI that runs the full test suite on every merge or pull request - on GitLab or GitHub, on hosted runners or your own machine - with the JUnit report eng-kit reads, cancel-on-new-push, a test database in RAM and a nightly random-order run. Use when the person asks to set up CI, a runner, a self-hosted runner, or to make tests run automatically on merge requests.

How it works

SKILL.md has no level-two headings · 23 lines, 264 words

SKILL.md preview
---
name: setup-ci
description: Set up CI that runs the full test suite on every merge or pull request - on GitLab or GitHub, on hosted runners or your own machine - with the JUnit report eng-kit reads, cancel-on-new-push, a test database in RAM and a nightly random-order run. Use when the person asks to set up CI, a runner, a self-hosted runner, or to make tests run automatically on merge requests.
disable-model-invocation: true
argument-hint: "[gitlab | github]"
---

# /eng-kit:setup-ci

1. **Find the host.** `git remote get-url origin` (github.com → GitHub, otherwise GitLab), or take `$ARGUMENTS`.
2. **Read what exists.** `.gitlab-ci.yml` or `.github/workflows/*.yml`. If there is CI already, never replace it:
   propose only the missing pieces as a diff (test job, JUnit report, cancel-on-new-push, nightly random order).
3. **Start from the template** for the stack:
   - GitLab + Laravel: `${CLAUDE_PLUGIN_ROOT}/skills/setup-ci/templates/gitlab-ci.laravel.yml`
   - GitHub + Laravel: `${CLAUDE_PLUGIN_ROOT}/skills/setup-ci/templates/github-actions.laravel.yml`
   - Other stacks: keep the same structure and swap the test command for the one in `.eng-kit/config.json`
     (`test_command`), so it writes JUnit XML; see `testing-standard/references/ci.md`.
   Show the exact file and wait for an explicit yes before writing it, on a new branch.
4. **Runner.** Ask which runner the person wants:
   - **Hosted** (GitLab shared runners / GitHub `ubuntu-latest`): nothing to install; uses CI minutes.
   - **Own machine**: give the owner steps from `references/runners.md` for their host. Steps in the GitLab or GitHub
     UI, and registering with the runner token, are **the person's to do**: never ask for, read, print or store a
     runner or registration token, and never paste one into a command line yourself. You may check afterwards that the
     runner container or service is running (`docker ps`, `./svc.sh status`) and that jobs show the runner's name.
5. **Security.** If they choose their own machine, say plainly: every job of the project will run on it; keep the
   project private, push access limited to trusted people and bots; never on a public GitHub repository.
6. **Measure.** After the first green run: `/eng-kit:import-ci latest`, then `/eng-kit:status`. If the project has no
   eng-kit data yet, run `/eng-kit:init` first.
Files in this package (4)
  • SKILL.md 2 KB
  • references/runners.md 5 KB
  • templates/github-actions.laravel.yml 3 KB
  • templates/gitlab-ci.laravel.yml 3 KB

Versions

RepositoryScoreLicence
This page · mahmoudissmail/eng-kit86MIT
wyeworks/accountable-review100MIT
SteveGJones/ai-first-sdlc-practices100MIT

Database snapshot: 13.11.2026 · package version 8c7c288c29ca (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100github-actions-test-jobs
    Use whenever the task is to run tests in GitHub Actions: a test workflow on pull requests, matrix builds across OS and runtime versions, splitting a suite across parallel runners, service containers such as Postgres or Redis, uploading JUnit reports, and trigger filters.
  • 100rseng-ci-cd
    Covers continuous integration and delivery for research software: CI/CD concepts, automating builds and tests with GitHub Actions and GitLab CI/CD, and wiring an organization's GitLab CI infrastructure to a GitHub-hosted project. Use when the user asks to set up CI, write a…
  • 100incus-gha-runners
    Set up, extend and troubleshoot GitHub Actions self-hosted runners on one Linux host, each runner in its own long-lived unprivileged Incus system container with its own Docker. Use when someone wants several self-hosted runners on one machine without them interfering, wants to…
  • 100speed-playbook
    How to make a slow test suite and a slow release flow faster without weakening tests - read eng-kit's measurements, find where the time goes, and plan the changes in a safe order (measure, setup once, boot less, parallel and isolation, test database, CI runner and pipeline,…
  • 100setup-playwright-ci
    Generates a GitHub Actions workflow that runs Playwright end-to-end tests on every pull request. The workflow provisions a PostgreSQL database via Testcontainers, installs Chromium, runs the full E2E suite, and uploads trace artifacts on failure. Use when the user asks to "set…
  • 90cmk:cicd
    Use when the user asks to "set up CI", "speed up CI", "add a deploy workflow", "structure GitHub Actions", "self-hosted runners", "persistent runner fleet", "runner pool", "runner capacity", "runner concurrency", "runner parallelism", "multi-project CI host", "runner isolation",…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.