agentleFS
Sign inStart free
ezmichaelyezmichaely/make-it-ezy/.agents/skills/ci-before-push/SKILL.md

ci-before-push

Skill0 starsChanged 9 days agoMITView on GitHub

Run Make It Ezy's GitHub CI gates locally before any git push or PR update. Use whenever the user asks to push, open/update a PR, merge to main, or "check CI" / "run gates" / "before push" on this repo — even if they did not name this skill. Do not push until check:ci is green.

  • Commits and pushes

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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. Distinctive:

    Never git push (or open/update a PR that needs a push) for this repo until the local CI mirror passes.

    line 12
  2. Very specific:

    Run pnpm check:ci (full/unsandboxed shell — CLI tests need tsx IPC).

    line 35
  3. Distinctive:

    If it fails: fix the reported errors, re-run until exit 0.

    line 36
  4. Distinctive:

    Only then commit (if needed) and push / create PR.

    line 37
  5. Very specific:

    Treat local lint alone as enough when dist/ already exists from an old build — always use pnpm check:ci

    line 44

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

Never git push (or open/update a PR that needs a push) for this repo until the local CI mirror passes.

Gate (must match .github/workflows/ci.yml)

From repo root:

pnpm check:ci

That runs, in order:

  1. pnpm build — required first so type-aware ESLint can resolve workspace dist/*.d.ts
  2. pnpm lint — ESLint strictTypeChecked
  3. pnpm typecheck
  4. pnpm test
  5. pnpm audit --prod --audit-level=high

CodeQL is GitHub-only; skip locally.

Procedure

  1. Confirm cwd is the make-it-ezy repo root.
  2. Run pnpm check:ci (full/unsandboxed shell — CLI tests need tsx IPC).
  3. If it fails: fix the reported errors, re-run until exit 0. Do not push red.
  4. Only then commit (if needed) and push / create PR.
  5. Tell the user the gate result in one line (pass/fail + first failing step).

Do not

  • Push “to see if CI passes”
  • Reorder or skip steps to save time
  • Treat local lint alone as enough when dist/ already exists from an old build — always use pnpm check:ci
  • Rely on vendored .agents/skills for tests — they change on every skills update; use temp fixtures

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