guidewire-local-dev-loop

Iterate on Gosu rules and configuration without paying the full 5–15 minute runServer rebuild every time. Use when standing up Guidewire Studio against a local InsuranceSuite instance, attaching an IntelliJ remote debugger to runServer, distinguishing changes that hot-reload from changes that force restart, or building a GUnit-driven TDD cycle for rule logic. Trigger with "guidewire studio", "gosu hot reload", "gosu debugger", "gunit", "guidewire runServer".

Ir a la instalación

Repositorio: jeremylongshore/tons-of-skills-marketplace
Última actividad en el origen: 19 de agosto de 2026 a las 12:13
Idioma detectado de SKILL.md: inglés
Estrellas: 2677
Forks: 392

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace --skill guidewire-local-dev-loop

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Explorador de archivos

3 archivos

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

langchain-deploy-integration

Deploy a LangChain 1.0 / LangGraph 1.0 app to Cloud Run, Vercel, or LangServe correctly — with timeouts sized for chain length, cold-start mitigation, SSE anti-buffering headers, and Secret Manager over .env. Use when prepping a first production deploy, debugging a stream that hangs behind a proxy, or diagnosing p99 latency spikes. Trigger with "langchain deploy", "langchain cloud run", "langchain vercel python", "langchain langserve", or "langchain docker".

2026-08-26

langchain-langgraph-agents

Build a correct LangGraph 1.0 ReAct agent with create_react_agent — typed tools, error propagation, recursion caps, and stop conditions that actually stop. Use when writing a first tool-calling agent, migrating from AgentExecutor or initialize_agent, or diagnosing an agent that loops on vague prompts. Trigger with "langgraph agent", "create_react_agent", "langgraph tool calling", "AgentExecutor migration", or "agent loop cost".

2026-08-26

langchain-langgraph-human-in-loop

Build LangGraph 1.0 human-in-the-loop approval flows with interrupt_before / interrupt_after and Command(resume=...) — JSON-serializable state, clean resume semantics, and UI wiring for approval decisions. Use when adding an approval gate before an expensive tool call, wiring a Slack/web UI for agent approvals, or debugging a graph that crashes on interrupt. Trigger with "langgraph human in loop", "langgraph interrupt_before", "langgraph approval flow", "Command resume", "langgraph HITL".

2026-08-26

Ver todos los de este repositorio

name	guidewire-local-dev-loop
description	Iterate on Gosu rules and configuration without paying the full 5–15 minute runServer rebuild every time. Use when standing up Guidewire Studio against a local InsuranceSuite instance, attaching an IntelliJ remote debugger to runServer, distinguishing changes that hot-reload from changes that force restart, or building a GUnit-driven TDD cycle for rule logic. Trigger with "guidewire studio", "gosu hot reload", "gosu debugger", "gunit", "guidewire runServer".
allowed-tools	Read, Write, Edit, Bash(gradle:), Bash(java:), Bash(jdb:*), Grep, Glob
version	1.25.0
license	MIT
author	Jeremy Longshore <jeremy@intentsolutions.io>
compatibility	Designed for Claude Code
tags	["guidewire","gosu","studio","hot-reload","gunit","debugging"]

Guidewire Local Dev Loop

Overview

Run a local InsuranceSuite instance and iterate on Gosu rule logic in seconds, not minutes. The single biggest productivity killer in Guidewire development is paying the 5–15 minute gradle runServer cold-start cost on every change because the developer does not know which edits hot-reload and which force a restart.

Three production problems this skill prevents:

Restart cascade — developer changes a Gosu rule, restarts runServer, waits 8 minutes, finds the rule was wrong, repeats. A full day disappears in restarts.
Silent stale code — Studio claims it hot-reloaded a class but the running JVM is still executing the old bytecode (common when interfaces change). Tests pass against stale code.
GUnit drift — unit tests for Gosu rules diverge from the rules themselves because the cycle to run a single test through Studio is too slow; developers stop writing them.

Prerequisites

JDK 17 (for Cloud release 202503+)
Guidewire Studio installed (IntelliJ-based, distributed by Guidewire)
Local InsuranceSuite configuration zone (PolicyCenter, ClaimCenter, or BillingCenter)
≥16 GB RAM on the dev machine — runServer + Studio + the JVM debug agent need headroom
Sample data loader configured for the chosen product (e.g., PersonalAuto for PC)

Instructions

Build the inner loop in this order. Every step targets one of the three productivity killers above.

1. Start runServer once, keep it warm

Cold start takes 5–15 minutes; treat it as a session investment.

# Start in dev mode with debug agent on 8088, leaves the server attached to the terminal
./gradlew runServer -Pdebug=true -PdebugPort=8088 -Dgw.servermode=dev

gw.servermode=dev enables the hot-reload paths inside the JVM. debugPort=8088 exposes the JDWP debug agent — attach IntelliJ to it once and leave it. Restart only when the what hot-reloads table below says you must.

2. What hot-reloads, what does not

Memorize this table — it determines whether the next edit costs 0 seconds or 8 minutes.

Change type	Hot-reload?	Action
Gosu method body in an existing class

Symptom	Cause	Solution
Code change "saved" but breakpoint fires on old line numbers	hot-reload silently failed (interface change, plugin registry edit)	restart runServer; do not chase phantom bugs
`gradle runServer` hangs at `Starting server` for >20 min	full database rebuild from a recent schema change	check logs in `logs/PolicyCenter.log`; if schema migration is running, wait it out; if hung, `dropAndCreateDatabase`
GUnit test passes locally, fails in CI	dev database carries stale data the test depends on	tests must self-fixture (`@Before` loads needed entities); never trust ambient sample data
IntelliJ debugger drops every few minutes	runServer crashed and auto-restarted under a launcher	check `logs/PolicyCenter.log` for OOM; raise `-Xmx` in `gradle.properties`
Hot reload works on Day 1, stops working after a `git pull`	merged change touched the plugin registry without your local picking it up	restart; rebase pulls do not always invalidate the plugin cache
`ClassCastException` on a class you just edited	binary-incompatible change to a non-interface class (e.g., changed a public field type)	restart; field-type changes are interface-equivalent for the JVM
Breakpoint set in Gosu, never hits	the rule path is not actually exercised by the test action	verify in `logs/PolicyCenter.log` that the rule fired; common cause is rule conditions filtering out the test data
Studio shows red error markers everywhere after pulling main	dependency cache stale	`./gradlew clean compileGosu` (don't `clean` the whole project — it nukes runServer's database)

guidewire-local-dev-loop

Opciones de instalación

Revisa los archivos de origen

Guidewire Local Dev Loop

Overview

Prerequisites

Instructions

1. Start runServer once, keep it warm

2. What hot-reloads, what does not

Guidewire Local Dev Loop

Overview

Prerequisites

Instructions

1. Start runServer once, keep it warm

2. What hot-reloads, what does not

3. Attach the IntelliJ debugger once per session

4. GUnit cycle for rule TDD

5. Sample data isolation per session

Output

Examples

Example 1 — Pure rule edit, zero restart

Example 2 — Interface change, controlled restart

Example 3 — TDD cycle on a new validation rule

Error Handling

See Also

Resources

guidewire-local-dev-loop

Datos de origen

Opciones de instalación

Revisa los archivos de origen

Más de este repositorio

Más de este repositorio

Guidewire Local Dev Loop

Overview

Prerequisites

Instructions

1. Start runServer once, keep it warm

2. What hot-reloads, what does not

Guidewire Local Dev Loop

Overview

Prerequisites

Instructions

1. Start runServer once, keep it warm

2. What hot-reloads, what does not

3. Attach the IntelliJ debugger once per session

4. GUnit cycle for rule TDD

5. Sample data isolation per session

Output

Examples

Example 1 — Pure rule edit, zero restart

Example 2 — Interface change, controlled restart

Example 3 — TDD cycle on a new validation rule

Error Handling

See Also

Resources