Defines engineering loops and security protocols for CI/CD and secret leakage prevention.
Install
mkdir -p .claude/skills/ci-cd-jgreen021 && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/19198" && unzip -o skill.zip -d .claude/skills/ci-cd-jgreen021 && rm skill.zipInstalls to .claude/skills/ci-cd-jgreen021
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
This standard defines the "Inner vs. Outer Loop" lifecycle and the defensive protocols for preventing resource sprawl and security leaks.Key capabilities
- →Distinguish between Inner Loop (local) and Outer Loop (Jenkins) execution tiers
- →Enforce pre-push gauntlet for Git operations
- →Audit for secret leaks before `git push`
- →Ensure plain-text secrets are never committed
- →Troubleshoot common CI/CD issues
- →Redact leaked secrets if detected
How it works
This skill defines a two-tier execution model (Inner/Outer Loop) and mandates a pre-push gauntlet including unit tests, static analysis, and a critical secret leak audit. It halts operations and redacts files if secrets are detected.
Inputs & outputs
When to use ci-cd
- →Setting up CI/CD pipelines
- →Auditing for leaked secrets
- →Defining local development loops
About this skill
Skill: CI/CD Strategy & Secret Protection
This standard defines the "Inner vs. Outer Loop" lifecycle and the defensive protocols for preventing resource sprawl and security leaks.
1. The Engineering Loops
To maintain high velocity and protect host resources, we distinguish between two execution tiers.
Tier 1: The Inner Loop (Local JVM/NPM)
- Goal: Sub-second feedback.
- Requirement: Never use Docker for logic verification. Run via
./gradlew test(Backend) ornpm test(UI). - Infrastructure: Keep support services (Oracle, Kafka, Vault) UP in a long-running, stable container set. Never restart these for logic changes.
Tier 2: The Outer Loop (Jenkins)
- Goal: Final quality gate and registry deployment.
- Execution: Triggered via Git push. Runs the Sovereign Jenkins Pipeline.
2. The "Agent's Pre-Push Gauntlet"
Before initiating a git push, the agent MUST execute and pass this checklist. Failure to do so constitutes an engineering violation.
| Step | Action | Command |
|---|---|---|
| Logic | Unit & Integration Tests | ./gradlew test |
| Style | Static Analysis | ./gradlew checkstyleMain |
| Safety | Secret Leak Audit | `git diff --cached |
| Integrity | Build Verification | ./gradlew bootJar |
3. Zero Secret Leak Mandate
- Rule: Plain-text secrets MUST NEVER be committed to source code or property files (
.properties,.yml,.json,.ts). - Storage: All credentials must reside in Sovereign Vault.
- Audit: If an agent detects a leaked secret in a local file, it MUST halt, notify the user, and redact the file before proceeding.
4. Troubleshooting Guardrails
- Connection Refused: Do not rebuild images. Verify
.envport mappings and container status withdocker ps. - Out of Memory: Check for "Zombie Daemons." Run
./gradlew --stopanddocker system prune -f(if images > 10). - Broken Pipe: Verify
/var/run/docker.sockvisibility in the development environment.
When not to use it
- →When Docker is used for logic verification in the Inner Loop
- →When plain-text secrets are intentionally committed to source code
- →When troubleshooting by rebuilding images for connection refused errors
Limitations
- →Plain-text secrets MUST NEVER be committed to source code or property files
- →Requires all credentials to reside in Sovereign Vault
- →Agent MUST halt and notify user if a leaked secret is detected
How it compares
This skill enforces a strict pre-push checklist with secret auditing and a clear distinction between local and CI/CD environments, preventing common security and resource sprawl issues before code is committed.
Compared to similar skills
ci-cd side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| ci-cd (this skill) | 0 | 3mo | Review | Intermediate |
| secrets-management | 5 | 3mo | Review | Advanced |
| supply_chain_security | 0 | 4mo | Review | Intermediate |
| odoo-image-supply-chain | 0 | 3mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jgreen021
View all by jgreen021 →You might also like
secrets-management
wshobson
Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentials, rotating secrets, or securing CI/CD environments.
supply_chain_security
zerAda
Docker image signing (Cosign), SBOM generation, SLSA provenance attestation, GHCR registry management.
odoo-image-supply-chain
Insightpulseai
Close container image supply-chain gap with automated ACR builds, vulnerability scanning, and image signing
bazel-build-optimization
wshobson
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
deployment-pipeline-design
wshobson
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing GitOps practices.
k8s-helm
rohitg00
Manage Helm charts, releases, and repositories. Use for Helm installations, upgrades, rollbacks, chart development, and release management.