executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
devsecopsApply DevSecOps practices, focusing on automated SAST/DAST scanning within CI/CD pipelines.
Independent GitHub snapshot · Automated classification · Original documentation governs
Embed security directly into CI/CD pipelines to catch vulnerabilities early. Focus on Static Application Security Testing (SAST), Dynamic Application Security Testing (DAST), and Secret Scanning.
%%{init: {"theme": "default", "flowchart": {"useMaxWidth": true}}}%%
flowchart TD
A[Push Code] --> B[Lint & Unit Test]
B --> C{Security Scans}
C -->|SAST| D[Semgrep / CodeQL]
C -->|Secrets| E[TruffleHog / Gitleaks]
C -->|Dependencies| F[Dependabot / Trivy]
D & E & F --> G{Gate}
G -->|Pass| H[Build Image]
G -->|Fail| I[Block PR]
H --> J[DAST Scan]
J --> K[Deploy]
name: DevSecOps Pipeline
on: [push, pull_request]
jobs:
security-scans:
runs-on: ubuntu-latest
steps:
- name: Checkout Code
uses: actions/checkout@v4
- name: Secret Scanning (TruffleHog)
uses: trufflesecurity/trufflehog@main
with:
path: ./
base: ${{ github.event.repository.default_branch }}
head: HEAD
extra_args: --only-verified
- name: SAST Scanning (Semgrep)
uses: returntocorp/semgrep-action@v1
with:
config: "p/default"