Menu
Design and optimize DevSecOps CI/CD pipelines with security gates, SAST, DAST, and container scanning
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run chaos security engineering tests — AI agent attempts to hack the Sprint output and reports findings to the team
Validate Java and TypeScript code against banking naming conventions, style rules, quality standards, and secure coding practices
Perform OWASP Top 10 security assessments, vulnerability scanning, and PCI-DSS compliance checks
Design test strategies including security testing, write test plans, and identify test scenarios for banking features with DevSecOps integration
Perform STRIDE threat modeling during Sprint Planning for new features and APIs
Run UX review checklist for banking user flows, validate WCAG accessibility compliance, assess security UX patterns, and review customer interface design
| name | pipeline-design |
| description | Design and optimize DevSecOps CI/CD pipelines with security gates, SAST, DAST, and container scanning |
Invoke when designing, reviewing, or optimizing the CI/CD DevSecOps pipeline.
Developer Commit
→ Pre-commit hooks (git-secrets)
→ Build (Gradle/Vite)
→ SAST (SonarQube + Snyk Code)
→ Unit Tests (JUnit 5 / Vitest)
→ Integration Tests (Testcontainers)
→ Dependency Scan (Snyk Open Source)
→ Container Build + Scan (Snyk Container)
→ Deploy to Staging
→ DAST (OWASP ZAP against staging)
→ Smoke Tests
→ Manual Approval (prod only)
→ Deploy to Production (Blue/Green)
→ Post-deploy monitoring
jobs:
build-and-scan:
steps: [checkout, build, sast, unit-test]
integration-test:
needs: build-and-scan
steps: [integration-test, dependency-scan]
deploy-staging:
needs: integration-test
steps: [container-build, container-scan, deploy-staging, dast]
deploy-prod:
needs: deploy-staging
if: github.ref == 'refs/heads/main'
steps: [manual-approval, blue-green-deploy, smoke-test]