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.
SkillScore68Maintained
Automatic
◆DevOps & SRE packguidewireci-cddeployment
Last verified 8/30/2026
What it changes
Passed 13 of 19 test cases with the skill, and 5 of 19 without it.
Without skill27%
With skill68%
Checks it passed that the model alone missed
Specifies a 95% to 5% canary traffic split ratio.
Mandates packageConfig as the Gradle task for packaging.
Specifies configuration.zip as the output artifact file name.
and 13 more in the full report
9 fixed6 passed either way7 still failing0 broke
Pass-rate lift
+41 pp
Tokens
+87%
Agent turns
0%
Response time
-22%
Model gemini-3.6-flashMeasured 8/30/2026v115 of 22 cases passed with skill · 19 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 7
Prompt
A defect was discovered in production 20 minutes after a Guidewire PolicyCenter deployment. The incident commander wants to immediately revert the GCC deployment package. What pre-check must be performed before deciding whether simple package reversion is sufficient?
What was checked, without and with the skill
Checked
Without skill
With skill
Requires querying the integration_audit table to detect bound resources prior to package reversion.
Missed
Passed
case-10 · gemini-3.6-flash · 8/30/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md214 lines3 files
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:
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.
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.
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.
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.
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. Each step targets one of the five production failures listed in Overview.
1. PR-time gates (run on every push)
Three checks, all blocking. The PR cannot merge to main if any fails.