team-shinchan:devops
npx machina-cli add skill seokan-jeong/team-shinchan/devops --openclawFiles (1)
SKILL.md
1.4 KB
EXECUTE IMMEDIATELY
Step 1: Validate Input
If args is empty or only whitespace:
Ask user: "What DevOps/infrastructure work would you like me to do?"
STOP and wait for user response
If args length > 2000 characters:
Truncate to 2000 characters
Warn user: "Request was truncated to 2000 characters"
Step 2: Execute Task
Do not read further. Execute this Task NOW:
Task(
subagent_type="team-shinchan:masao",
model="sonnet",
prompt=`/team-shinchan:devops has been invoked.
## DevOps/Infrastructure Request
Handle infrastructure tasks including:
| Area | Capabilities |
|------|-------------|
| CI/CD | GitHub Actions, Jenkins, GitLab CI |
| Containers | Docker, Kubernetes, docker-compose |
| Cloud | AWS, GCP, Azure configuration |
| Monitoring | Logging, metrics, alerting setup |
| Environments | Dev, staging, production configs |
## Implementation Requirements
- Follow Infrastructure as Code principles
- Include automated testing in pipelines
- Use proper secret management
- Document configuration changes
- Test locally before deploying
- Implement blue-green or canary deployments where appropriate
User request: ${args || '(Please describe the DevOps task)'}
`
)
STOP HERE. The above Task handles everything.
Source
git clone https://github.com/seokan-jeong/team-shinchan/blob/main/skills/devops/SKILL.mdView on GitHub Overview
Team Shinchan:devops automates DevOps and infrastructure tasks using Masao. It covers CI/CD, Docker/Kubernetes, cloud configuration, monitoring, and environment setup, all driven by Infrastructure as Code and automated testing. This ensures repeatable, secure deployments from Dev to production.
How This Skill Works
Inputs are validated and truncated if needed, then a Task is dispatched to the Masao subagent to execute the requested DevOps work. It leverages IaC principles, automated tests in pipelines, proper secret management, and deployment strategies (blue-green/canary) to deploy across Dev, staging, and production.
When to Use It
- Setting up a CI/CD pipeline with GitHub Actions, Jenkins, or GitLab CI
- Configuring containerized deployments using Docker, Kubernetes, or docker-compose
- Provisioning and configuring cloud resources on AWS, GCP, or Azure
- Implementing centralized monitoring, logging, metrics, and alerting
- Designing blue-green or canary deployment strategies for safe rollouts
Quick Start
- Step 1: Describe your DevOps task in the input (args) field
- Step 2: The system validates input, truncates to 2000 characters if needed, and warns if truncated
- Step 3: The task is executed by Masao (team-shinchan:masao) to implement CI/CD, containers, and cloud infra as specified
Best Practices
- Follow Infrastructure as Code principles for all changes and store configs in version control
- Incorporate automated testing within pipelines to validate builds and deployments
- Use proper secret management; avoid hard-coded credentials in configs or scripts
- Document configuration changes and rollback procedures for each deployment
- Test changes locally or in a staging environment before deploying to production; plan canary/blue-green deployments when appropriate
Example Use Cases
- Create a GitHub Actions workflow to build Docker images, push to a registry, and deploy to Kubernetes with canary updates
- Provision AWS infrastructure via IaC (Terraform/CloudFormation) and deploy a microservice stack
- Set up centralized logging (ELK/CloudWatch) and metrics with alerting for a production app
- Migrate a monolithic app to containerized services using docker-compose and Kubernetes manifests
- Implement secret rotation and secure secret storage within CI/CD pipelines
Frequently Asked Questions
Add this skill to your agents