BenkapnerBenkapner/claude-code-basecamp/skills/ci-guard/SKILL.md

ci-guard

Skill17 starsChanged 59 days agoMITView on GitHub

Use when starting work in a repository under repositories/ that may lack CI configuration. Detects missing CI workflows (GitHub Actions, GitLab CI, CircleCI) and alerts the user to add one. Skips repos marked as research-only.

1 other project uses a version of this.

Adopted by

Most recently taken up by

Abdox-menara/guard-skillstheir own version, first seen Aug 24, 2026

Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
Abdox-menara/guard-skills★ 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 repository9 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- brainstormingSkill
- cost-speed-meterSkill
- python-patternsSkill
- refactoring-patternsSkill
- security-checkSkill
- semantic-versioningSkill
- update-docsSkill
- verification-loopSkill

The file

We split this skill into the rules it gives an agent

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

≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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

Very specific:
When a user clones or creates a new repo under repositories/
line 14
Very specific:
When running /verify or /quality-gate in a repo without CI
line 15
Distinctive:
Run the check script against any repo:
line 19
Distinctive:
When CI is missing and the repo is not research:
line 49

≈ “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

CI Guard

Repositories benefit from CI, but this skill is advisory. It checks for CI configuration and alerts when it is missing, while allowing research, prototypes, and intentionally local projects.

When to Activate

At session start, after repository status is reported
When a user clones or creates a new repo under repositories/
When running /verify or /quality-gate in a repo without CI

How to Check

Run the check script against any repo:

uv run skills/ci-guard/scripts/check-ci.py <repo-path>

The script checks for common CI indicators and the research exemption.

CI Indicators (any one is sufficient)

Provider	Path
GitHub Actions	`.github/workflows/` (with at least one `.yml`/`.yaml`)
GitLab CI	`.gitlab-ci.yml`
CircleCI	`.circleci/config.yml`
Jenkins	`Jenkinsfile`
Travis	`.travis.yml`
Azure	`azure-pipelines.yml`

Research Exemption

A repo is exempt from the CI requirement if:

A .research file exists in the repo root, OR
pyproject.toml contains purpose = "research" in [project.optional] or as a comment marker

To mark a repo as research: touch <repo>/.research

Alert Behavior

When CI is missing and the repo is not research:

Warn clearly at session start: "This repo has no CI configuration."
Suggest a starter workflow based on the detected stack (Python/Node/Rust/Go)
Reference the basecamp's own CI (.github/workflows/ci.yml) as a working template
Do not block work - this is an alert, not a gate

Starter Templates

Python (uv-based, matching basecamp conventions)

name: CI
on:
  pull_request:
    branches: [main]
  push:
    branches: [main]

jobs:
  lint:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: astral-sh/setup-uv@v6
      - run: uv python install 3.12
      - run: uv sync --group dev
      - run: uv run ruff check .
      - run: uv run ruff format --check .

  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: astral-sh/setup-uv@v6
      - run: uv python install 3.12
      - run: uv sync --group dev
      - run: uv run pytest -v

Node.js

name: CI
on:
  pull_request:
    branches: [main]
  push:
    branches: [main]

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: 20
      - run: npm ci
      - run: npm run lint
      - run: npm test

Common Mistakes

Mistake	Fix
Forgetting CI on quick prototype repos	Use `.research` file for true prototypes, add CI for everything else
Adding CI but not running tests	CI without tests is a false safety net - at minimum lint
Blocking the user from working	This is an alert, not a blocker - warn and continue

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.

Check your setup, free