Agent skill · software engineering · jeremylongshore
guidewire-ci-cd-pipeline
Ship Gosu code and configuration changes through Guidewire Cloud Console deployment slots without breaking running policies — Gosu compile + GUnit + lint gates per PR, config-package promotion dev→UAT→prod, schema-change rollouts with rollback hazards documented, canary deploy for high-risk changes, and the rollback decision tree when a release affects already-bound policies. Use when designing the deploy pipeline for a new InsuranceSuite project, hardening an existing one, or recovering from a bad release. Trigger with "guidewire ci cd", "guidewire deploy", "guidewire promotion", "guidewire slots", "guidewire rollback".
Why this skill is useful
Adds a comprehensive CI/CD pipeline with specific commands and rollback strategies tailored for Guidewire, which are not commonly found in public documentation.
What it needs
Requires curl, git, gradle, jq installed locally. Requires github, gitlab account access. About 8k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Guidewire CI/CD Pipeline Overview Ship Gosu changes from a developer's branch to production without breaking running policies. Guidewire Cloud Console (GCC) deployment slots are the carrier-side promotion mechanism — dev → uat → prod — with config packages as the unit of promotion. The CI side validates compile, runs GUnit, and packages; the CD side promotes packages through slots with deploy-time gates. Five production failures this skill prevents: 1. Bypassed compile/test gates — a gradle build failure on a developer's machine reaches CI as "works on my machine"; CI runs the same gates as a clean clone, fails fast, never lands on a slot. 2. Promotion without UAT regression — UW logic change goes dev → prod skipping UAT; the change interacts badly with a product line not exercised in dev; bound policies start showing wrong premium. 3. Schema change without rollback plan — a Gosu interface adds a required field; rolling back the deploy is fine, but rolling back the database column requires a separate migration that may have been forgotten. 4. Canary that isn't a canary — "canary" deploy serves 100% of traffic immediately because the slot router has no per-slot routing; a real canary needs traffic split, not just a separate slot. 5. Rollback after policies bound on the new code — a defective rate-plan deploy bound 200 policies in the 30 minutes before detection; reverting the code does not unbind the policies; they need targeted endorsement-correction or rate adjustment. Prerequisites A working Guidewire Studio + runServer setup per guidewire-local-dev-loop GCC tenant with at least three slots (dev, uat, prod) configured for the integration's product line A CI runner (GitHub Actions, GitLab CI, Jenkins) with JDK 17 and access to a private artifact registry for config packages An age private key (per guidewire-security-and-rbac) provisioned to CI for decrypting environment-specific secrets Instructions Build the pipeline in this order. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/guidewire-ci-cd-pipeline--010ae7