DevOps Engineer Skills
A streamlined automation suite for DevOps tasks covering build, container, and release management.
Install
mkdir -p .claude/skills/devops-engineer-skills && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15299" && unzip -o skill.zip -d .claude/skills/devops-engineer-skills && rm skill.zipInstalls to .claude/skills/devops-engineer-skills
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.
Consolidated skill set for the DevOps Engineer agent — Maven build, Docker, GitHub Actions, CI/CD orchestration, and release managementKey capabilities
- →Build Java projects with Maven
- →Containerize applications using Docker
- →Manage GitHub Actions workflows
- →Perform static code analysis with PMD
- →Generate JaCoCo code coverage reports
- →Handle release management tasks
How it works
The skill orchestrates Maven commands for building and testing Java applications, Docker commands for containerization, and defines GitHub Actions workflows for continuous integration and deployment.
Inputs & outputs
When to use DevOps Engineer Skills
- →Building and packaging Java apps
- →Containerizing services with Docker
- →Managing CI/CD release workflows
About this skill
DevOps Engineer — Skill Definition
1. Maven Build
No
mvnw— always invokemvndirectly.
SetREPSY_ACCOUNT_USER+REPSY_ACCOUNT_PASSWORDbefore any Maven command.
mvn -DskipTests compile # fast compile check
mvn test # full build: tests + PMD + JaCoCo
mvn -DskipTests package # produce target/backbone-rest.jar
mvn test jacoco:report # generate coverage report
mvn pmd:check pmd:cpd-check # static analysis only
mvn deploy -s ci_settings.xml # publish to Repsy
Repsy Private Repository
<!-- ci_settings.xml already configured; expose as env vars in CI -->
REPSY_ACCOUNT_USER=<user>
REPSY_ACCOUNT_PASSWORD=<password>
Maven annotation processing (MapStruct):
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<source>21</source><target>21</target>
<annotationProcessorPaths>
<path>
<groupId>org.mapstruct</groupId>
<artifactId>mapstruct-processor</artifactId>
<version>1.5.5.Final</version>
</path>
</annotationProcessorPaths>
</configuration>
</plugin>
2. Docker Containerization
- Base image:
amazoncorretto:21-alpine3.20 - Port exposed:
8082 - JAR:
target/backbone-rest.jar(must be built before Docker)
mvn -DskipTests package
docker build -t lamata/backbone-rest .
docker build -t lamata/backbone-rest:1.2.0 .
docker push lamata/backbone-rest
Certificate Import at Build Time
RUN keytool -importcert -alias wildcard-tst \
-file /certs/wildcard.tst.crt \
-keystore $JAVA_HOME/lib/security/cacerts \
-storepass changeit -noprompt
Certs imported: prx-qa.crt, prx-qa.manager.crt, srmn.crt, prx-qa.config-server.crt
Runtime Environment Variables
docker run -p 8082:8082 \
-e APP_PORT=8082 \
-e APP_TOKEN_SECRET=<base64-secret> \
-e SSL_KEYSTORE_LOCATION=/certs/keystore.jks \
-e SSL_KEYSTORE_PASSWORD=<password> \
-e SSL_KEYSTORE_TYPE=JKS \
-e VAULT_TOKEN=<token> \
-e VAULT_SERVER_URL=https://vault.prx.tst \
-e AUTH_SERVER_URI=https://keycloak.prx.tst/realms/prx \
-e AUTH_CERT_URI=/protocol/openid-connect/certs \
-e SPRING_BOOT_PROFILE_ACTIVE=qa \
lamata/backbone-rest
Image Hardening
RUN addgroup -S appgroup && adduser -S appuser -G appgroup
USER appuser
HEALTHCHECK --interval=30s --timeout=10s --retries=3 \
CMD curl -f http://localhost:8082/actuator/health || exit 1
3. GitHub Actions
# .github/workflows/ci.yml
name: CI Pipeline
on:
push:
branches: [main, develop]
pull_request:
branches: [main]
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Set up JDK 21
uses: actions/setup-java@v4
with:
java-version: '21'
distribution: 'corretto'
cache: 'maven'
- name: Build and Test
run: mvn test -s ci_settings.xml
env:
REPSY_ACCOUNT_USER: ${{ secrets.REPSY_ACCOUNT_USER }}
REPSY_ACCOUNT_PASSWORD: ${{ secrets.REPSY_ACCOUNT_PASSWORD }}
- name: Package
run: mvn -DskipTests package
- name: Upload coverage report
if: always()
uses: actions/upload-artifact@v4
with:
name: jacoco-report
path: target/site/jacoco/
Required GitHub Secrets
| Secret | Purpose |
|---|---|
REPSY_ACCOUNT_USER | Maven private dependency resolution |
REPSY_ACCOUNT_PASSWORD | Maven private dependency resolution |
DOCKER_USERNAME | Docker Hub push |
DOCKER_TOKEN | Docker Hub authentication |
4. Quality Gates
| Gate | Tool | Failure Condition |
|---|---|---|
| Static Analysis | PMD 3.23.0 | Any violation → build fails |
| Copy-Paste Detection | PMD CPD | Any duplication → build fails |
| Unit Tests | JUnit 5 | Any test failure → build fails |
| Coverage Report | JaCoCo 0.8.12 | Report failure (minimum = 0%) |
| SonarCloud | sonarcloud.io | Manual review only |
5. Release Management
Release Checklist
- [ ] All tests pass (mvn test)
- [ ] No PMD violations
- [ ] JaCoCo report generated
- [ ] OpenAPI spec updated for any API changes
- [ ] CHANGELOG updated
- [ ] No critical/high CVEs in dependencies
- [ ] Docker image built and pushed
- [ ] Git tag created: v{MAJOR}.{MINOR}.{PATCH}
Tagging
git tag -a v1.2.0 -m "Release v1.2.0"
git push origin v1.2.0
Required Environment Variables
| Variable | Purpose |
|---|---|
APP_PORT | Server port (default 8082) |
APP_TOKEN_SECRET | JWT signing secret (Base64) |
APP_TOKEN_EXPIRATION | JWT expiration in ms |
SSL_KEYSTORE_LOCATION | Keystore classpath location |
SSL_KEYSTORE_PASSWORD | Keystore password |
SSL_KEYSTORE_TYPE | JKS |
SSL_TRUSTSTORE_LOCATION | Truststore path |
SSL_TRUSTSTORE_PASSWORD | Truststore password |
VAULT_TOKEN | HashiCorp Vault token |
VAULT_SERVER_URL | Vault server URL |
CNFS_URI / CNFS_PORT | Config Server |
AUTH_SERVER_URI | Keycloak issuer URI |
AUTH_CERT_URI | Keycloak JWK set URI suffix |
AUTH_CLIENT_ID | OAuth2 client ID |
AUTH_CLIENT_SECRET | OAuth2 client secret |
SPRING_BOOT_PROFILE_ACTIVE | Active Spring profile |
REPSY_ACCOUNT_USER | Repsy Maven repo user |
REPSY_ACCOUNT_PASSWORD | Repsy Maven repo password |
When not to use it
- →When `mvnw` is preferred over `mvn`
- →When Docker base image is not `amazoncorretto:21-alpine3.20`
- →When not using GitHub Actions for CI/CD
Prerequisites
Limitations
- →The skill always invokes `mvn` directly, not `mvnw`.
- →The Docker base image is `amazoncorretto:21-alpine3.20`.
- →Quality gates are defined for PMD, CPD, JUnit 5, and JaCoCo.
How it compares
This skill consolidates various DevOps tools and practices into a unified interface, simplifying the setup and execution of build, containerization, and CI/CD processes compared to managing each tool separately.
Compared to similar skills
DevOps Engineer Skills side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| DevOps Engineer Skills (this skill) | 0 | 3mo | Review | Advanced |
| deployment-engineer | 4 | 4mo | No flags | Advanced |
| devops-engineer | 1 | 3mo | Review | Advanced |
| devops-engineer | 0 | 3mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
deployment-engineer
sickn33
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization. Use PROACTIVELY for CI/CD design, GitOps implementation, or deployment automation.
devops-engineer
Jeffallan
Use when setting up CI/CD pipelines, containerizing applications, or managing infrastructure as code. Invoke for pipelines, Docker, Kubernetes, cloud platforms, GitOps.
devops-engineer
I-Synergy
DevOps and CI/CD specialist. Use for building pipelines, containerization, infrastructure as code, or deployment automation. User-invocable only for production deployments.
platform-engineering
villadalmine
>-
add-linux-bootstrap-platform
ponylang
Load when adding a new Linux distro/version (e.g. Alpine 3.24, Ubuntu 26.04) — or both arches for an existing one — as a fully supported ponyup bootstrap-test target. Covers the bootstrap-tester Dockerfile, image build dispatch and tag discovery, CI workflow updates (tier 1 / tier 2), ponyup-init.sh
production-dockerfile
phenobarbital
Generate production-ready Dockerfiles with multi-stage builds, security best practices, and optimization. Use when containerizing Python applications for production deployment.