From cms-cultivator
Automates Kanopi's Drupal/Pantheon DevOps onboarding: creates GitHub repos, configures Pantheon services, and sets up CI/CD pipeline. Requires explicit user confirmation for each irreversible phase.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cms-cultivator:devops-setupThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Automate Kanopi's complete Drupal/Pantheon DevOps onboarding workflow using the drupal-pantheon-devops-specialist agent.
Automate Kanopi's complete Drupal/Pantheon DevOps onboarding workflow using the drupal-pantheon-devops-specialist agent.
This skill makes irreversible changes across multiple systems:
kanopi/ organizationExplicit user confirmation is required before each destructive phase. This skill will pause and confirm before creating the GitHub repo, before Pantheon configuration, and before pushing any code.
/devops-setup [git-url]Arguments: Git URL (Pantheon SSH or GitHub HTTPS/SSH)
gh) installed and authenticated with kanopi org accessWhen Task() or system tools are unavailable:
.ddev/config.yaml, .circleci/config.yml, phpstan.neon, etc. based on project infoWhen running in Claude Code with Task() and all required tools:
⚠️ CONFIRM WITH USER before spawning the agent — this is an irreversible multi-system setup.
Present to user:
DevOps Setup will:
1. Create new GitHub repo: kanopi/{repo-name}
2. Configure branch protection and teams
3. Enable Redis and New Relic on Pantheon (may incur costs)
4. Make code changes and create feature/kanopi-devops branch
5. Create PR
Reply "confirm" to proceed, or "cancel" to abort.
After user confirms:
Task(cms-cultivator:drupal-pantheon-devops-specialist:drupal-pantheon-devops-specialist,
prompt="Set up Kanopi DevOps for a Drupal/Pantheon project. Arguments: {git-url if provided}. Follow the complete 5-phase workflow: (1) Clone repo and create new GitHub repo in kanopi org, (2) Configure GitHub settings (squash merge, branch protection, teams), (3) Configure Pantheon services via Terminus (Redis, New Relic), (4) Make all code changes on feature/kanopi-devops branch, (5) Push branch, create PR, and output verification checklist with manual follow-up tasks.")
kanopi/ orgpantheon (original) + origin (new kanopi repo)main branch and pushkanopicode16 code changes including: DDEV config, Composer dev deps + scripts, code quality configs, pantheon.yml, Cypress tests, CircleCI config, CODEOWNERS, Quicksilver scripts, README, CLAUDE.md
feature/kanopi-devops branchTERMINUS_TOKEN, GITHUB_TOKEN, etc.npx claudepluginhub kanopi/claude-toolbox --plugin cms-cultivatorScaffolds test + deploy CI/CD pipelines for GitHub Actions, GitLab CI, Jenkins, and targets like Vercel, Netlify, Docker after assessing user's git host and deploy setup. Teaches basics to beginners.
Generates a complete CI/CD pipeline with lint, test, build, deploy, and verify stages. Detects project type and recommends GitHub Actions, Vercel, Railway, or Docker-based deployment.
Generates CI/CD workflows, Dockerfiles, and deployment configs from a tech stack definition. Use when scaffolding infrastructure for a project.