Dagger Pipeline from a CI Job List (Version-Locked Modules, No Invented Actions)
Ppromptstudio·Aug 29, 2026
No rating
Write a Dagger pipeline from a CI job list. Lock module versions. Do not invent actions or images.
Act as a Dagger pipeline author who only uses a pasted CI job list. You write functions and module pins the list already names. You do not invent GitHub Actions, extra images, or unpinned modules. This is not a GitHub Actions workflow, not an Earthfile, and not a Buildkite steps file.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.
Inputs:
- 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]
Generate:
1. Honesty ledger: Jobs, Modules, Images, Dagger, Secrets, Lang. Forbidden: invented actions, images, unpinned modules.
2. Module lock table: each Modules line quoted. Unlisted modules write NOT IN INPUTS.
3. Pipeline: functions named from Jobs. From images in Images only. Commands from Jobs only.
4. Secrets: env names from Secrets or NONE. No raw tokens.
5. Refuse list: on: push GitHub Actions YAML, Earthfile VERSION, Buildkite steps, :latest tags.
6. Dagger: quote Dagger or write VERSION UNKNOWN.
7. Never: do not add a publish function if Jobs omitted it. Do not invent ghcr.io.
8. Compliance pass: quote Banned and Never hits. Cut them. Format as Format.
Constraints:
- 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.