agentleFS
kaandgnshkaandgnsh/Claude-Blue/skills/devsecops/release-gate/SKILL.md

release-gate

Skill0 starsChanged 11 days agoMITView on GitHub

Define and operate security release gates in CI/CD — which checks block (new critical SAST/SCA/secret/IaC findings, unsigned artifacts, missing provenance), thresholds, exception workflow and metrics — so security is enforced without blocking delivery on legacy debt. Use when designing pipeline security policy, tuning a gate that blocks too much, or approving a release with open findings.

10 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Security Release Gate

Gate design principles

  1. Gate on new risk, report on old: block PRs/releases that introduce critical findings; track existing backlog separately with SLAs.
  2. High-signal checks only block; noisy checks warn until tuned.
  3. Exceptions are explicit (ticket, approver, expiry) and visible in the pipeline log.
  4. Same policy everywhere via reusable workflows/templates; changes to gate config require security review (CODEOWNERS).

Typical gate matrix

CheckTool examplesBlock when
Secretsgitleaks, GitHub push protection, trufflehogAny verified/live secret
SASTSemgrep, CodeQLNew high/critical with confirmed rule precision
SCAosv-scanner, Dependabot, TrivyNew dependency with KEV/critical reachable vuln, or malicious package
IaCCheckov, Trivy configNew high/critical misconfig
Container imageTrivy, GrypeCritical fixable vulns in base image; image not from approved registry
Supply chaincosign verify, SLSA provenance verifyUnsigned artifact or provenance mismatch at deploy
DAST (staging)ZAP baselineHigh-confidence high findings
PolicyOPA/Kyverno at deployPrivileged workloads, latest tags

Exception record

Finding | Release | Reason | Compensating control | Approver | Expiry | Ticket — pipeline reads an allow-list file (in repo, CODEOWNERS-protected) keyed by finding fingerprint with expiry date; expired entries fail the gate.

Metrics

Gate pass rate, mean time blocked, exceptions count/age, escaped vulnerabilities (found in prod that the gate should have caught).

Related skills

sast-triage, sca-dependency-risk, iac-scanning, artifact-signing, vuln-exception-review

References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.