GitHub Actions taste — ChatGPT prompt for CI setup
The GitHub Actions taste ChatGPT prompt sets out practices for building CI with GitHub Actions. It covers checks, releases, and deployment safeguards.
CC0-1.0 ★ 178,201 updated 2026-10-24
Open on GitHubWhat GitHub Actions taste does
The prompt lays out a GitHub Actions CI approach: keep workflows in .github/workflows/, run checks on pull requests and pushes to the default branch, and run tests, linting, and type checks as parallel jobs. A single required status should collect their results before a merge.
It also recommends pinning third-party actions to full commit SHAs, using minimal permissions:, caching by lockfile hash, and cancelling outdated PR runs with cancel-in-progress: true. Secrets belong in repository or environment secrets, not workflow YAML or logs, and must stay out of workflows for fork PRs from untrusted contributors. Other recommendations cover GitHub Environments with required reviewers, actionlint, failure artifacts, signed images, and tag-based releases. The Claude Code path is .claude/commands/prompts.csv.md.
What it helps with
- configure checks for pull requests and the default branch
- combine test and lint results into a required status
- limit token permissions and protect CI secrets
- set up signed container publishing and tag-based releases
Example prompts for the agent
- Draft a GitHub Actions workflow for my repository with parallel tests, linting, and type checks.
- Review my workflow for violations of GitHub Actions security practices.
- Propose a CI plan to build and publish a container image with provenance and a signature.
How to install GitHub Actions taste
How to use
Paste the text at the start of a chat or into project instructions
Manually: put the files in place
.claude/commands/prompts.csv.mdQuestions about GitHub Actions taste
How do I install GitHub Actions taste in ChatGPT?
Use it as a text prompt in ChatGPT by including its recommendations in a request about setting up GitHub Actions.
What does GitHub Actions taste do?
It provides guidance for CI, pull request checks, secret handling, deployments, and releases with GitHub Actions.
How does the prompt recommend storing GitHub Actions secrets?
Store them as repository secrets or environment secrets. Keep them out of workflow YAML and logs, and do not expose them to workflows for fork PRs from untrusted contributors.
Source text
prompts.csv · CC0-1.0
# GitHub Actions taste of a CI-first platform engineer - Keep every workflow under `.github/workflows/` in the same repo as the code it builds, and name files after the job they do, such as `ci.yml` or `release.yml`. Confidence: 0.95 - Trigger pull-request CI on `pull_request` and push to the default branch; avoid `workflow_dispatch`-only pipelines for checks that must block merges. Confidence: 0.90 - Pin third-party actions to a full commit SHA, and leave the version in a comment so upgrades are deliberate. Confidence: 0.90 - Prefer official `actions/*` and verified publishers; treat unknown marketplace actions as untrusted code. Confidence: 0.85 - Run unit tests, lint and typecheck in parallel jobs, and make the merge gate wait on a single required status that aggregates them. Confidence: 0.85 - Cache package managers with the official cache action keyed on the lockfile hash, and do not cache build outputs that must stay hermetic. Confidence: 0.80 - Use the smallest hosted runner that finishes in a few minutes; move heavy builds to larger runners only after measuring. Confidence: 0.75 - Put secrets in repository or environment secrets, never in workflow YAML, logs or fork PRs from untrusted contributors. Confidence: 0.95 - Use GitHub Environments with required reviewers for production deploys, and separate staging from production. Confidence: 0.85 - Prefer OIDC federated credentials to cloud providers over long-lived access keys stored as secrets. Confidence: 0.90 - Fail the job on the first real error; do not use `continue-on-error` to hide flaky steps you have not fixed. Confidence: 0.85 - Upload test reports, coverage and traces as artifacts on failure so reviewers can debug without re-running locally. Confidence: 0.85 - Keep workflow YAML short: extract shared steps into a composite action or a reusable workflow under `.github/workflows/`. Confidence: 0.80 - Set explicit `permissions:` to the least privilege each job needs; never leave the default write-all token when read is enough. Confidence: 0.90 - Concurrency-group PR workflows with `cancel-in-progress: true` so only the latest commit runs. Confidence: 0.85 - Run `actionlint` and a workflow schema check in CI so broken YAML never reaches the default branch. Confidence: 0.80 - Build and push container images from CI with provenance (SLSA) and sign them; do not publish from a laptop. Confidence: 0.80 - Keep release automation on tagged commits with changelog generation, and block force-pushes to release tags. Confidence: 0.85 - Document how to run the same checks locally in CONTRIBUTING so developers are not surprised by CI-only failures. Confidence: 0.80 - Review Dependabot or Renovate PRs for action bumps the same week they open; stale pins become security debt. Confidence: 0.75
© f · CC0-1.0 · f/prompts.chat