heyeddi-ci-runners
Skill0 starsChanged 3 months agoMITView on GitHub
Configure HeyEddi Spot runners — prefer GHA overflow/always with the HEYEDDI_RUNS_ON hook; author sealed eddi-ci.yaml pipeline jobs only for no-GHA or niche checks. Use when wiring runners, pipeline YAML, or Spot CI.
In this repository51 other files it gives its agents.
- .cursor/rules/skill-authoring.mdcCursor rule
- backend-type-bridgerSkill
- composable-patternsSkill
- dart-type-bridgerSkill
- design-handoff-flutterSkill
- design-system-generalizerSkill
- engineering-excellenceSkill
- flutter-engineeringSkill
- flutter-patternsSkill
- heyeddi-designSkill
- heyeddi-handoffSkill
- heyeddi-intakeSkill
- heyeddi-orchestratorSkill
- heyeddi-productSkill
- heyeddi-pr-respondSkill
- heyeddi-pr-reviewSkill
- no-duplicate-uiSkill
- pre-merge-gateSkill
- primevue-openprops-architectSkill
- project-engineeringSkill
- ux-flow-auditorSkill
- verify-buildSkill
- visual-auditorSkill
- backend-type-bridgerSkill
- composable-patternsSkill
- dart-type-bridgerSkill
- design-handoff-flutterSkill
- design-system-generalizerSkill
- engineering-excellenceSkill
- flutter-engineeringSkill
- flutter-patternsSkill
- heyeddi-ci-configSkill
- heyeddi-ci-failsSkill
- heyeddi-ci-guideSkill
- heyeddi-designSkill
- heyeddi-handoffSkill
- heyeddi-intakeSkill
- heyeddi-orchestratorSkill
- heyeddi-productSkill
- heyeddi-pr-respondSkill
- heyeddi-pr-reviewSkill
- heyeddi-setupSkill
- heyeddiSkill
- no-duplicate-uiSkill
- pre-merge-gateSkill
- primevue-openprops-architectSkill
- project-engineeringSkill
- taste-penpotSkill
- ux-flow-auditorSkill
- verify-buildSkill
- visual-auditorSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 6 are distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 20
Golden rule: Never duplicate the same test/build in GHA and pipeline:.
- Distinctive: line 27
Ensure every Linux job uses:
- Very specific: line 37
Keep eddi-ci.yaml Reviewer-only with pipeline: {} (use @heyeddi-ci-config).
- Very specific: line 48
Prefer @heyeddi-ci-config for the create/update decision gate.
- Distinctive: line 55
Before any summary that implies execution, run:
- Distinctive: line 81
Never secrets in YAML
- Distinctive: line 82
Never invent test commands
- Distinctive: line 84
Never merge without authorize merge
- Distinctive: line 85
Never claim correlated AI+runner timeline (Coming soon)
≈ “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.
Files
HeyEddi CI Runners
Spot is shipped. Help the user wire the right runner path and never invent execution claims.
Two job kinds (do not collapse)
| Kind | Where | Check name | When to use |
| GHA on Spot | .github/workflows/*.yml + workspace gha_spot_mode | Same workflow Check | Repos that already have Actions (default) |
Sealed pipeline: | eddi-ci.yaml pipeline: jobs | HeyEddi Runner: {job_id} | No (or minimal) GHA, or niche sealed checks |
Golden rule: Never duplicate the same test/build in GHA and pipeline:. Prefer GHA + Spot routing; keep pipeline: {}.
Product docs: https://ci.heyeddi.com/docs · hub mirrors: see reference/runners.md.
Prefer GHA overflow / always
- Confirm
.github/workflows/exists (or user wants Actions-based CI). - Ensure every Linux job uses:
runs-on: ${{ vars.HEYEDDI_RUNS_ON || 'ubuntu-latest' }}- Tell the user to set workspace Runners mode on ci.heyeddi.com:
overflow— GitHub minutes first; Spot JIT when exhaustedalways— Linux jobs on Spot from the first runoff— hosted only
- Keep
eddi-ci.yamlReviewer-only withpipeline: {}(use@heyeddi-ci-config). - Limits: Linux only; private repos; prepaid/entitled workspace; platform kill switch is ops-owned. Overflow reliability can still gap — do not promise “always works.”
Sealed pipeline: (advanced / no-GHA)
load_policy_contract— living knobs only.inspect_repo— evidenced commands + path prefixes; never inventpytest/npm test.- Explicit user opt-in (billable runner time).
- Author argv-safe
run(no shell operators,sudo,curl,wget), catalogimage,filter.pathswhen possible. - Jobs run on Spot when the workspace is entitled and Spot env is live; they post
HeyEddi Runner: {job_id}Checks.
Prefer @heyeddi-ci-config for the create/update decision gate.
Evidence rule (mandatory)
- Jobs can run under entitlement + Spot substrate.
- A job did run only when you have Check / Spot evidence (
HeyEddi Runner: …, workflow Check conclusion, Ops/logs). - YAML lint ≠ execution. Unknown → say so and use
@heyeddi-ci-fails. - Before any summary that implies execution, run:
assert_runners_claims --check --agent-text "<your summary>"Pipeline
load_policy_contract
inspect_repo
→ choose GHA-first vs sealed pipeline (never both for the same CI)
→ wire HEYEDDI_RUNS_ON hook and/or author pipeline: jobs
assert_runners_claims --check --agent-text "<your summary>"Tools
| Tool | Purpose |
load_policy_contract | Living knobs / guide |
inspect_repo | Languages + evidenced commands |
assert_runners_claims | Block unsubstantiated execution claims |
Safety
- Never secrets in YAML
- Never invent test commands
- Never
auto_merge - Never merge without authorize merge
- Never claim correlated AI+runner timeline (Coming soon)
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
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.

