kanopi/devops-setup
skills/devops-setup/SKILL.md
Automate Kanopi's complete Drupal/Pantheon DevOps setup for a new project. Invoke when user explicitly asks to set up DevOps for a new project, onboard a Pantheon site to Kanopi's CI/CD pipeline, or uses /devops-setup. This is an irreversible multi-system setup requiring explicit user confirmation at each phase. Creates GitHub repos, configures Pantheon services, and makes code changes.
$ install --global
skillsauthnpx skillsauth add kanopi/cms-cultivator devops-setupInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 19, 2026, 5:01 AM8.6s2 files scanned
SKILL.md
- name:
- devops-setup
- description:
- Automate Kanopi's complete Drupal/Pantheon DevOps setup for a new project. Invoke when user explicitly asks to set up DevOps for a new project, onboard a Pantheon site to Kanopi's CI/CD pipeline, or uses /devops-setup. This is an irreversible multi-system setup requiring explicit user confirmation at each phase. Creates GitHub repos, configures Pantheon services, and makes code changes.
- disable-model-invocation:
- true
DevOps Setup
Automate Kanopi's complete Drupal/Pantheon DevOps onboarding workflow using the drupal-pantheon-devops-specialist agent.
⚠️ Side Effect Warning
This skill makes irreversible changes across multiple systems:
- Creates a new GitHub repository in the
kanopi/organization - Configures branch protection rules and GitHub teams
- Enables Pantheon services (Redis, New Relic) — may incur costs
- Makes code changes across 16 files and creates new branches/PRs
- Installs new Composer dependencies
Explicit 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.
Usage
- "Set up DevOps for this Pantheon project"
- "Onboard this site to Kanopi's CI/CD pipeline"
/devops-setup [git-url]
Arguments: Git URL (Pantheon SSH or GitHub HTTPS/SSH)
Prerequisites
- Git installed and configured
- GitHub CLI (
gh) installed and authenticated withkanopiorg access - Terminus CLI installed (or will be installed automatically)
- Write access to Pantheon site
- Pantheon site UUID
Environment Detection
Tier 1 — Portable (Claude Desktop, Codex, any environment)
When Task() or system tools are unavailable:
- Gather inputs — Ask user for: Git URL, GitHub org, Pantheon site name/UUID, team members
- Plan phases — Present the complete 5-phase setup plan for review
- ⛔ STOP: Wait for user confirmation to proceed with each phase
- Provide manual instructions — Step-by-step commands for each phase:
- Phase 1: Clone repo and create GitHub repo commands
- Phase 2: GitHub settings configuration commands
- Phase 3: Pantheon Terminus commands
- Phase 4: Code change checklist (16 steps)
- Phase 5: Branch creation and PR commands
- Generate config files — Use Write to create
.ddev/config.yaml,.circleci/config.yml,phpstan.neon, etc. based on project info
Tier 2 — Claude Code Enhanced
When 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.")
Workflow Phases
Phase 1: Initial Git Setup
- Clone from provided git URL
- Create new private GitHub repo under
kanopi/org - Configure remotes:
pantheon(original) +origin(new kanopi repo) - Create
mainbranch and push
Phase 2: GitHub Configuration
- Enable squash merges, auto-delete branches, auto-merge
- Create GitHub team with write access +
kanopicode - Set branch protection: require PR reviews, status checks, conversation resolution
Phase 3: Pantheon Configuration
- Verify/install Terminus CLI
- Enable Redis and New Relic on Pantheon site
- Retrieve site UUID for CircleCI config
Phase 4: Code Changes (feature/kanopi-devops branch)
16 code changes including: DDEV config, Composer dev deps + scripts, code quality configs, pantheon.yml, Cypress tests, CircleCI config, CODEOWNERS, Quicksilver scripts, README, CLAUDE.md
Phase 5: PR Creation
- Push
feature/kanopi-devopsbranch - Create PR with comprehensive description
- Output verification checklist and manual follow-up tasks
Manual Follow-Up Tasks (Always Required)
- CircleCI Secrets: Configure
TERMINUS_TOKEN,GITHUB_TOKEN, etc. - CircleCI SSH Key: Add SSH key to Pantheon for deployments
- Gulp Upgrade: Upgrade Gulp 3 to 4 if flagged
- Theme Compilation: Verify theme builds on multidev
Related Skills
- pr-create — Create PRs for subsequent changes
- quality-audit — Analyze code quality after setup
- security-audit — Run security audit on the project
Related Skills
kanopi/strategist-site-audit
tools
VerifiedTrustedCommunity
Strategist-focused site audit for discovery and pre-discovery. Given a site URL and optional qualitative research data, navigates the site via CoWork, audits against all 21 UX Laws from lawsofux.com, reviews content hierarchy, synthesises qualitative data, runs Lighthouse, and produces two deliverables — a Project Knowledge Summary (Markdown for Claude Desktop Projects) and a polished, iterable HTML Artifact for client sharing. Use when a strategist, UX lead, or PM asks for a discovery audit, UX laws audit, content hierarchy review, pre-discovery site review, "audit this site for strategy", "strategist audit", "UX audit", or pastes a site URL with discovery context. Not for developer audits — use accessibility-audit, performance-audit, or live-site-audit for those.
11SKILL.mdUpdated May 15, 2026
kanopi/story-point-estimator
development
VerifiedTrustedCommunity
Provide story point estimation guidance with hour calculations for software development tasks. Uses Fibonacci sequence (1, 2, 3, 5, 8, 13, 21, 34+) and converts story points to hours. Includes platform-specific adjustments and velocity calculations.
11SKILL.mdUpdated May 15, 2026
kanopi/qa-review
tools
VerifiedTrustedCommunity
Perform a full QA review of a Teamwork task by reading the task and all its comments for context, extracting the multi-dev URL, generating dynamic validation steps tailored to the task type, and using CoWork browser automation to execute those steps on the multi-dev environment. Produces a structured validation report with pass/fail per step, screenshots, internal notes, and a client-facing summary — all shown in chat. Use this skill whenever the user asks to QA, test, validate, or review a Teamwork task or multi-dev environment — even if they just say "can you QA this?" or paste a Teamwork link. Also triggers for phrases like "run QA on", "check the multi-dev", "validate this task", "test the dev link", or "review the ticket". Works across Drupal/CMS updates, WordPress/plugin updates, bug fixes, new feature development, and general web development tasks.
11SKILL.mdUpdated May 15, 2026
kanopi/project-heartbeat
tools
VerifiedTrustedCommunity
Generate a client-facing project heartbeat / status update message for a Kanopi project, ready to be posted as a Teamwork message. Use this skill whenever the user asks to write, draft, generate, or send a project update, heartbeat, status update, or progress report to a client. Also triggers when the user says things like "time for a project update", "draft the heartbeat", "write up the update for [project]", or "it's been two weeks, let's send an update". Always use this skill — even if the user doesn't say "heartbeat" — whenever the intent is to summarise recent project activity for a client audience.
11SKILL.mdUpdated May 15, 2026