platform-ci-cd

Guides creation and review of CI/CD pipelines with security gates and release evidence.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/pnewsam/skills --skill platform-ci-cd-pnewsam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: platform-ci-cd
Source: https://github.com/pnewsam/skills/tree/main/archive/platform-compliance-evicted/platform-ci-cd
Command: npx skills add https://github.com/pnewsam/skills --skill platform-ci-cd-pnewsam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? CI/CD pipelines often ship with broad permissions, mutable dependencies, untested artifacts, and no release evidence, creating security and reliability risks. This Skill provides structured guidance for building, reviewing, and fixing continuous integration and delivery workflows so the safest path becomes the default. ## Core Features & Use Cases - Pipeline Guardrails: Enforces build-once-test-then-deploy patterns, least-privilege workflow permissions, and separation of untrusted PR validation from trusted deployment jobs. - Supply Chain Hardening: Covers pinned actions and images, SLSA-style provenance attestations, short-lived OIDC credentials, and protection against running untrusted code with secrets. - Review Checklist & Decision Rubric: Provides concrete criteria for triggers, artifacts, permissions, evidence, and rollback paths when auditing existing workflows. - Use Case: When reviewing a GitHub Actions workflow that deploys to production, use this Skill to verify the deploy job uses the exact tested artifact, has minimal permissions, and records release evidence. ## Quick Start Review my GitHub Actions deployment workflow for permission, artifact, and supply-chain issues using the platform-ci-cd guidance.

Frequently Asked Questions about platform-ci-cd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I secure GitHub Actions workflow permissions?▼

Set workflow permissions to read-only by default and escalate only at the job level where needed. Use short-lived OIDC credentials instead of static cloud keys, and separate untrusted PR validation from privileged deployment workflows.

How do I ensure deployments use the tested artifact?▼

Build the artifact once, run tests against it, and deploy that exact immutable artifact identified by commit SHA and digest. Never rebuild on production hosts or deploy whatever happened to be on the main branch.

What is SLSA provenance in CI/CD pipelines?▼

SLSA provenance is an attestation linking an artifact to its build process, source commit, and dependencies. It lets you verify that released artifacts came from the expected pipeline and were not tampered with.

Why is running untrusted PR code with secrets dangerous?▼

Pull request code from forks can exfiltrate repository secrets or cloud credentials if the workflow grants them access. Split untrusted PR validation from trusted deployment jobs and never expose secrets to unreviewed code.

When should I pin GitHub Actions and Docker images?▼

Pin critical third-party actions and images to specific versions or digests, especially for privileged or release-critical steps. Mutable tags like latest can silently change behavior or introduce compromised code into your pipeline.