How to Write a Dagger Pipeline from a CI Job List
Dagger pipelines rot when they From alpine:latest and add actions/checkout. The job list locked golang:1.23.2-bookworm. Quote that tag.
The matching generator is the Dagger Pipeline from a CI Job List (Version-Locked Modules, No Invented Actions) (Dagger Pipeline From Ci Job List Version Locked Modules No Invented Actions) prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled run survives, share the version you actually use (Share a prompt).
Print the module and image lock table first
Write a Dagger pipeline from a CI job list. Lock module versions. Do not invent actions or images. Start by filling Inputs, not by asking the model to remember last week's run. If a field is blank, write NONE or NOT IN INPUTS and leave it blank through Generate. The card is built so the model cannot honestly invent a number, owner, URL, or command that you did not paste.
Paste these fields before you hit run:
CI job list I lock (job names, commands I allow): [Jobs]
Modules I lock with versions: [Modules]
Base images I lock: [Images]
Dagger version I lock (or UNKNOWN): [Dagger]
Words I must not use: [Banned]
What I must never invent (actions, images, module versions): [Never]
Output format: [Format]
Language for comments: [Lang]
Secrets I allow as env names (or NONE): [Secrets]
That inventory is the honesty ledger. Anything that does not appear there is forbidden in the draft. If you catch yourself adding a nice-to-have after the run, you are no longer using the card. You are ghostwriting. Put the extra fact in Inputs and run again.
Write functions only from named jobs
Generate is numbered on purpose. Do not skip a step because the first paragraph looked done. The early steps exist to stop later prose from smuggling claims.
Walk the Generate list in order:
- Honesty ledger: Jobs, Modules, Images, Dagger, Secrets, Lang. Forbidden: invented actions, images, unpinned modules.
- Module lock table: each Modules line quoted. Unlisted modules write NOT IN INPUTS.
- Pipeline: functions named from Jobs. From images in Images only. Commands from Jobs only.
- Secrets: env names from Secrets or NONE. No raw tokens.
- Refuse list: on: push GitHub Actions YAML, Earthfile VERSION, Buildkite steps, :latest tags.
- Dagger: quote Dagger or write VERSION UNKNOWN.
- Never: do not add a publish function if Jobs omitted it. Do not invent ghcr.io.
- Compliance pass: quote Banned and Never hits. Cut them. Format as Format.
If a step asks for a version lock, quote the version from Inputs in the output. If a step asks for a refuse list, keep the refuse list in the published artifact, not in a sidebar you delete. Reviewers should see what the model was not allowed to do.
EXPOSE no GitHub Actions YAML
Most failures are the same shape: a missing field gets a confident fill. A conversion rate appears. A Gradle task appears. A flash point appears. A caption appears on a job that asked for slide text only. Your review is to search the draft for numbers, names, and commands, then grep Inputs. No match means cut.
Honor the constraints as hard stops, not vibes:
- Dagger pipeline from Jobs and Modules only. Not GitHub Actions and not Earthfile.
- Never invent actions, images, or module versions.
- Only Secrets named in Inputs.
- No emojis.
When the card says not legal advice, not certification, not an exam dump, or not a caption engine, that sentence belongs at the top of the output. Deleting it to look more finished is how you inherit risk.
Keep publish out if the job list omitted it
Finish with the compliance pass the prompt already asks for. Quote the banned-word hits. Cut them. Print character counts when the job has a cap. Print word counts when the job has a budget. List gaps as gaps. Five missing facts are more useful than one smooth paragraph.
Tags on the card (dagger pipeline ci jobs, version-locked modules, no invented actions) are a reminder of the job shape, not an invitation to wander into a neighboring cluster. If you need a different surface, open a different PromptDig card rather than stretching this one.
Fill the card, then run
Replace every bracket. Run on ChatGPT, Claude, or Gemini. Read the ledger first, then the artifact. If the model invents a commit, KPI, DOI, PEL, bid, or logo, discard the run. Tighten Inputs. Run again. Share the filled card that survived, not the first draft that sounded done.