agentleFS
frontier-ai-nextfrontier-ai-next/mgarlbot/skills/gitlab_pages_ci/SKILL.md

gitlab_pages_ci

Skill17 starsChanged 4 months agoMITView on GitHub

GitLab CI — test job and GitLab Pages job (artifact `public/`); `.gitlab-ci.yml` templates

  • Installs packages

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If .gitlab-ci.yml already exists — extend stages/jobs.

    line 75
  2. Very specific:

    After merge: Pages URL like https://<namespace>.gitlab.io/<project>/ (depends on settings).

    line 76

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

GitLab CI + Pages

The GitLab Runner executes the pipeline, not the bot. Your job is to add or fix .gitlab-ci.yml in the repo and list what to enable in GitLab (Settings → Pages, visibility).

General layout

  • stages: [test, deploy] (or [test, pages]).
  • test job: same stack as local (Python/Node/Go). Default image from process env GITLAB_CI_DEFAULT_IMAGE (e.g. python:3.12-bookworm) — use it in YAML if the project has no image:.
  • pages job: GitLab requires a public/ artifact. Build the static site (MkDocs, VitePress, sphinx -b html, SPA npm run build then copy into public/) and declare:
pages:
  stage: deploy
  needs: ["test"]
  script:
    - mkdir -p public
    - cp -r dist/* public/   # example; adapt to the project
  artifacts:
    paths:
      - public

Python (pytest) + minimal Pages stub

Template “tests + placeholder site”:

stages: [test, deploy]

variables:
  PIP_CACHE_DIR: "$CI_PROJECT_DIR/.cache/pip"

test:
  stage: test
  image: python:3.12-bookworm
  cache:
    paths: [.cache/pip]
  before_script:
    - python -m pip install -U pip
    - test -f requirements.txt && pip install -r requirements.txt || true
    - test -f pyproject.toml && pip install -e ".[dev]" || true
  script:
    - pytest -q || true

pages:
  stage: deploy
  needs: ["test"]
  image: alpine:latest
  script:
    - mkdir -p public
    - echo '<!doctype html><meta charset=utf-8><title>CI</title><p>GitLab Pages OK</p>' > public/index.html
  artifacts:
    paths: [public]

Tune pytest for the real layout (tests/, uv run, etc.).

Node / static frontend

  • image: node:22-bookworm (or project LTS).
  • cache: { paths: [node_modules/] }
  • script: npm ci && npm run build → output in dist/ or build/ → copy into public/.

Important

  • No secrets in YAML; use GitLab CI/CD Variables (masked).
  • If .gitlab-ci.yml already exists — extend stages/jobs; do not break production-branch deploy without explicit user approval.
  • After merge: Pages URL like https://<namespace>.gitlab.io/<project>/ (depends on settings); tell the user to check Deploy → Pages in the UI.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.