devops-devsecops

Build and secure CI/CD pipelines, containers, cloud infrastructure, and monitoring stacks.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/rhorba/RestoLedger --skill devops-devsecops-rhorba
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devops-devsecops
Source: https://github.com/rhorba/RestoLedger/tree/main/skills/devops-devsecops
Command: npx skills add https://github.com/rhorba/RestoLedger --skill devops-devsecops-rhorba

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Setting up secure CI/CD pipelines, hardened containers, cloud infrastructure, and monitoring from scratch is error-prone and time-consuming, and misconfigurations create security vulnerabilities that are costly to fix later. ## Core Features & Use Cases - CI/CD Pipeline Setup & Hardening: Ready-to-adapt GitHub Actions and GitLab CI templates with built-in security scanning (Semgrep, Trivy, Checkov, Gitleaks) and least-privilege permissions. - Container & Kubernetes Security: Secure Dockerfile templates, Pod Security Standards, network policies, and RBAC configurations for hardened deployments. - Cloud & IaC Security: Terraform starters, AWS/GCP/Azure security checklists, IAM least-privilege patterns, and compliance mappings (SOC 2, PCI-DSS, HIPAA, ISO 27001). - Use Case: You need to ship a new service. Use this Skill to generate a hardened GitHub Actions pipeline with SAST/SCA/container scanning, a non-root multi-stage Dockerfile, and a monitoring stack with essential alerts—then enforce the rule that nothing ships while CI is red. ## Quick Start Set up a secure CI/CD pipeline with security scanning and a hardened Dockerfile for my Node.js application.

Frequently Asked Questions about devops-devsecops

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

FAQPage Schema
How do I set up a secure CI/CD pipeline with GitHub Actions?

Use a workflow with restricted GITHUB_TOKEN permissions, then add jobs for secrets scanning with Gitleaks, SAST with Semgrep, dependency scanning with Trivy, and IaC scanning with Checkov. Pin actions by SHA and gate builds on all security jobs passing.

What security scanning tools should run in a CI pipeline?

Run Semgrep for SAST, Trivy for dependency and container image vulnerabilities, Checkov for Terraform and IaC misconfigurations, and Gitleaks for secrets detection. Configure each to fail the build on CRITICAL and HIGH severity findings.

How do I write a secure Dockerfile for production?

Use a multi-stage build with a minimal base image pinned by digest, create a non-root user, copy only built artifacts, add a HEALTHCHECK, and use tini as the init process. Exclude secrets and .git via .dockerignore and scan the final image with Trivy.

Does this approach work with GitLab CI as well as GitHub Actions?

Yes, hardened templates are provided for both GitHub Actions and GitLab CI covering secrets scanning, SAST, SCA, container scanning, and IaC checks. The same tools—Semgrep, Trivy, Checkov, and Gitleaks—run in either platform.

Why does my CI pipeline fail on Trivy container scans?

Trivy fails the build when it finds CRITICAL or HIGH severity vulnerabilities in the image or dependencies. Update the affected package or base image to a patched version, rebuild, and re-scan until the findings are resolved.

When should I use Kubernetes instead of Docker Compose?

Start with Docker Compose for development and single-server deployments, following the YAGNI principle. Move to Kubernetes only when you provably need auto-scaling, multi-node orchestration, or advanced rollout strategies that Compose cannot handle.