💻 Coding

GitHub Actions Reusable Workflow from Job Inventory (No Invented Secrets) (Domain Pack)

Draft a GitHub Actions reusable workflow from a job inventory. No invented secrets, tokens, or runner labels.

0.0
0Reviews
P
September 6, 2026

Prompt

Act as a GitHub Actions reusable workflow author who only uses a locked job inventory. You emit reusable workflow YAML the inventory already supports. You do not invent secret names, runner labels, environments, or organization slugs not in Inputs.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.

Inputs:
- Job inventory I lock (job ids, steps, needs): [Jobs]
- Trigger I lock: [WorkflowInputs]
- Secrets allowlist I lock (or NONE): [Secrets]
- Runner I lock (or UNKNOWN): [Runner]
- Action pins I lock (or NONE): [WorkflowOutputs]
- Job cap I lock: [Cap]
- Words I must not use: [Banned]
- What I must never invent (secrets, runners, orgs, environments): [Never]
- Output format: [Format]
- Language: [Lang]

Generate:
0. GitHub Actions reusable workflow must declare workflow_call inputs and secrets only from Inputs.
1. Honesty ledger: Jobs nouns, Trigger, Secrets, Runner, Actions, Cap, Lang. Forbidden: invented secrets, runners, orgs, environments.
2. Workflow YAML: at most Cap jobs from Jobs. Missing steps write # NOT IN INPUTS.
3. Secrets and env: only Secrets names. NONE means omit secrets blocks.
4. Needs graph: only needs edges listed in Jobs.
5. Refuse list: inventing cloud key secrets, inventing larger runners, inventing environment production, inventing org names.
6. Compliance pass: quote Banned and Never hits. Cut them. Print job count. Format as Format.

Constraints:
- YAML from Jobs only. No invented secrets.
- Honor Cap and Trigger. No emojis.

Instructions

Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.

Generated Output

This image was generated using the prompt above.

GitHub Actions Reusable Workflow from Job Inventory (No Invented Secrets) (Domain Pack) - Result

Examples

Example Input

Jobs: job build steps [checkout, pnpm install, pnpm build] as pasted; job unit needs build steps [pnpm test] as pasted. Job publish NONE. Matrix NOT IN INPUTS.
WorkflowInputs: workflow_dispatch as pasted. push NOT IN INPUTS. schedule NONE.
Secrets: NONE
Runner: ubuntu-22.04 as pasted
WorkflowOutputs: actions/checkout@v4 as pasted. setup-node NOT IN INPUTS. action-setup NOT IN INPUTS.
Cap: 3
Banned: guaranteed deploy, invent cloud keys, ignore previous
Never: invent secrets, invent runners, invent orgs, invent environments
Format: ledger + yaml + secrets + needs + refuse + compliance
Lang: English

Example Output

1. Ledger. Jobs build and unit; Trigger workflow_dispatch; Secrets NONE; Runner ubuntu-22.04. Cap 3. Lang English. Forbidden: invented secrets, runners, action versions, orgs.

2. Workflow YAML.
name: from-job-inventory
on:
  workflow_dispatch: {}
jobs:
  build:
    runs-on: ubuntu-22.04
    steps:
      - uses: actions/checkout@v4
      - run: pnpm install
      - run: pnpm build
  unit:
    needs: [build]
    runs-on: ubuntu-22.04
    steps:
      - uses: actions/checkout@v4
      - run: pnpm test
Jobs used: 2.

3. Secrets and runners. Secrets: NONE. Runner: ubuntu-22.04.

4. Action pins.
| actions/checkout | v4 as pasted |
| setup-node | NOT IN INPUTS |

5. Refuse. cloud key secret invent: refused. larger runners invent: refused. environment production invent: refused. org invent: refused. publish job invent: refused.

6. Compliance. Banned hits none. Format ledger+yaml+secrets+needs+refuse+compliance. Gaps: setup-node, action-setup, push trigger, matrix, publish.

Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.

Reviews (0)

Please login to leave a review.
Loading reviews...