Rules for organizing GitHub Actions, a service that runs automated checks when code changes. They define CI jobs, when each runs, how changes are detected, and how tests and coverage are connected.

Use them when adding or changing CI jobs, path filters, dependencies between checks, test gates, coverage reporting, or GitHub Actions workflows.

They make automated checks predictable and avoid running unnecessary jobs for documentation-only changes. They also ensure backend, frontend, integration, end-to-end, and generated-code checks are gated appropriately.

ci-workflow — Cursor rule for Cursor by golid-ai: Rules for organizing GitHub Actions, a service that runs…

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add rules/golid-ai/golid/ci-workflow

Clone the repo

git clone --depth 1 https://github.com/golid-ai/golid

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/rules/golid-ai/golid/ci-workflow.svg)](https://agentmods.dev/rules/golid-ai/golid/ci-workflow)

Your own site

<a href="https://agentmods.dev/rules/golid-ai/golid/ci-workflow"><img src="https://agentmods.dev/badge/rules/golid-ai/golid/ci-workflow.svg" alt="Measured on agentmods" height="20"></a>

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 2,091 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.02091
Opus 5	$0.00000	$0.01045
Sonnet 5	$0.00000	$0.00418
Haiku 4.5	$0.00000	$0.00209

Measured 3d ago against content hash 5457fdf51f46, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ci-workflow scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/ci-workflow.mdc · 124 lines

How it starts

The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CI Workflow Patterns

Thesis: CI catches what developers forget: type errors, test regressions, stale generated types, and vulnerable dependencies. Jobs must not have cross-job dependencies.

Job structure

Job	Gate	Depends on
`changes`	always	—
`spec-drift`	always	—
`backend-unit`	`run_backend`	`changes`
`backend-integration`	`run_backend`	`changes`, `backend-unit`
`backend-coverage`	`run_backend` + unit + integration OK	`changes`, `backend-unit`, `backend-integration`
`frontend`	`run_frontend`	`changes`
`scaffold-verify`	`run_backend \|\| run_frontend`	`changes`
`e2e`	`run_e2e` + integration + frontend OK	`changes`, `backend-integration`, `frontend`

changes uses dorny/paths-filter@v4 to compute run_backend, run_frontend, run_e2e. Docs-only PRs (docs/**, **/*.md except CHANGELOG.md) run changes + spec-drift only — backend, frontend, scaffold, and E2E are skipped. CHANGELOG-only commits run backend + frontend (Codecov refresh) without E2E. codecov.yml sets flag_management.default_rules.carryforward: true so docs-only pushes keep the last report on HEAD.

Workflow needs pull-requests: read for paths-filter on PRs.

Backend unit job checklist

No PostgreSQL — unit tests only
go build + go vet before tests
golangci-lint: pin to a version compatible with the Go version in go.mod
Unit tests split: pure packages without -race (apperror, config, pagination, retry, validate), then handler/middleware/observability/queue/service/testutil/wire with -race
Both unit runs use shared COVERPKG env and merge into coverage-unit.out
govulncheck: always run, fails CI on vulnerabilities
Upload coverage-unit.out as artifact (not Codecov yet)

Backend integration job checklist

PostgreSQL service container with health check (golid_test database)
Matrix shard: handler | service — each shard runs on a separate runner
go test -tags integration ./internal/${{ matrix.shard }}/... -race -count=1
Handler shard exits 0 with no packages when no handler integration tests exist — do not add skip hacks
Set TEST_DATABASE_URL only — testutil.SetupTestDB() panics if unset (no DATABASE_URL fallback)
TEST_MIGRATIONS_PATH: ${{ github.workspace }}/backend/migrations — per-package schemas via testutil, no global migrate step
Upload per-shard coverage-integration-{shard}.out as artifacts

Read the full file on GitHub · 124 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

3d ago First seen · 124 lines · 0 tokens per session scan A 5457fdf51f46

Subscribe to this mod's changes

ci-workflow is a cursor rule published in the GitHub repository golid-ai/golid (40 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,091 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

CI and CD DevOps and cloud echo go postgresql solidjs ssr

ci-workflow

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

CI Workflow Patterns

Job structure

Backend unit job checklist

Backend integration job checklist

What this file has done since we first saw it

Other cursor rules, from other repositories

state-management

40-deploy

beanstalk-deploy

test-headless-github-actions

infra-devops

testing-ci-rule