agentleFS
Sign inStart free
matteingmatteing/opal/.claude/skills/ci-preflight/SKILL.md

ci-preflight

Skill59 starsChanged 9 months agoMITView on GitHub

Runs the full CI check suite locally before pushing. Use this skill before pushing a branch or when the user asks to verify everything passes, to catch issues before they hit CI.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. n1m21n/Infinite★ 318same name
    2. The-Artificer-of-Ciphers-LLC/skills-from-the-artificer★ 6same name
    3. Marnie0415/pi-skills★ 1same 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.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before pushing a branch to remote.

    line 13
  2. Distinctive:

    When the user asks to "run CI", "check everything", or "preflight".

    line 14
  3. Distinctive:

    After a large set of changes to verify nothing is broken.

    line 15
  4. Distinctive:

    Run these in order. Stop and fix issues at each step before proceeding.

    line 19
  5. Distinctive:

    Every check must pass before pushing: If something fails, fix it first.

    line 57
  6. Distinctive:

    If a test is flaky (passes on retry), flag it to the user rather than silently retrying.

    line 60

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

You run the same checks that GitHub Actions CI performs, but locally, to catch failures before pushing. This saves time and keeps the commit history clean.

When to act

  • Before pushing a branch to remote.
  • When the user asks to "run CI", "check everything", or "preflight".
  • After a large set of changes to verify nothing is broken.

Check sequence

Run these in order. Stop and fix issues at each step before proceeding.

1. Elixir core

# Compile with warnings-as-errors (matches CI)
mise run build:core

# Check formatting
mise run lint:core

# Run tests
mise run test:core

2. TypeScript CLI

# Lint (ESLint)
mise run lint:cli

# Verify codegen is current
mix run scripts/codegen_ts.exs --check

# Build (typecheck + compile)
mise run build:cli

3. Quick summary

Or run everything at once:

mise run lint && mise run build && mise run test

Rules

  1. Every check must pass before pushing. If something fails, fix it first.
  2. Report results clearly — list what passed and what failed.
  3. For failures, diagnose the root cause and suggest or apply fixes.
  4. If a test is flaky (passes on retry), flag it to the user rather than silently retrying.

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