Agent skill

Guidewire Local Dev Loop

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Iterate on Gosu rules and configuration without paying the full 5–15 minute runServer rebuild every time.

MITAuto-check passedTesting & QA

Install Guidewire Local Dev Loop

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill guidewire-local-dev-loop -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace guidewire-local-dev-loop --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/guidewire-local-dev-loop .claude/skills/guidewire-local-dev-loop && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
guidewire-local-dev-loop
GitHub stars
2.8k
Token cost
~2.6k tokens
SKILL.md length
1,041 words
Files
3 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Iterate on Gosu rules and configuration without paying the full 5–15 minute runServer rebuild every time.

  • Works in 5 steps: Start runServer once, keep it warm → What hot-reloads, what does not → Attach the IntelliJ debugger once per… → …
  • Standing up Guidewire Studio against a local InsuranceSuite instance
  • SKILL.md covers Overview, Prerequisites, Instructions and Output, plus 4 more sections
  • Calls gradle and git

What it does

Guidewire Local Dev Loop is an agent skill from jeremylongshore/tons-of-skills-marketplace. 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".

Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/API_REFERENCE.md` and `references/implementation-guide.md`). Compatibility notes: Designed for Claude Code

It sits in Testing & QA, covering Test-driven development. It works with JetBrains IDEs. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • 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
  • Building a GUnit-driven TDD cycle for rule logic

Example prompts

  • “guidewire studio”
  • “gosu hot reload”
  • “gosu debugger”
  • “/guidewire-local-dev-loop”

Requirements

  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(gradle:*), Bash(java:*), Bash(jdb:*), Grep, Glob

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  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

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash(gradle:*)
    • Bash(java:*)
    • Bash(jdb:*)
    • Grep
    • Glob

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gradle
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • developer.guidewire.com
    • gosu-lang.github.io
    • docs.oracle.com
    • docs.gradle.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Guidewire Local Dev Loop loads about 2.6k tokens when it runs, and up to ~5.2k if it reads all its reference files. Until then it costs about 122 tokens; SKILL.md has 1,041 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~122
When it runs · the whole SKILL.md, loaded when a task matches
~2.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 1,041 words, ~2,585 tokens.

Download SKILL.mdSave it as .claude/skills/guidewire-local-dev-loop/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
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
compatibility
Designed for Claude Code
version
1.26.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
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:

  1. Restart cascade — developer changes a Gosu rule, restarts runServer, waits 8 minutes, finds the rule was wrong, repeats. A full day disappears in restarts.
  2. 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.
  3. 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.

bash
# 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 typeHot-reload?Action
Gosu method body in an existing classyessave in Studio; runServer detects via Reload Plugin
Gosu rule (entity, validation, UW) bodyyessave; rule fires on next entity event
New Gosu class added to an existing packageyessave; class is picked up on first reference
Gosu interface signature changenorestart runServer (binary-incompatible class load)
New Gosu plugin registerednorestart runServer (plugin registry is built once at boot)
PCF (Page Configuration Format) layout edityessave; refresh the browser
New PCF page added to the navigationpartialrestart usually; Reload Plugin sometimes works in dev mode
Database schema change (new column, new entity)norestart with gradle dropAndCreateDatabase runServer
Localization bundleyessave; refresh browser
Messaging destination / App Event pluginnorestart (plugin registry)
config/server.xml or config/plugin/registry/*.xmlnorestart

When in doubt, trust the JVM, not Studio. Open the IntelliJ debugger, set a breakpoint on the changed method, trigger the code path, and confirm the breakpoint hits the new line numbers. Studio's "reloaded" status is informational, not authoritative.

3. Attach the IntelliJ debugger once per session
Run > Edit Configurations > + > Remote JVM Debug
  Host: localhost
  Port: 8088
  Module classpath: <your-config-module>
  Save → run with the bug icon

Once attached, breakpoints survive Gosu hot-reloads. The connection drops only on full runServer restart. Use conditional breakpoints (policy.totalPremium.compareTo(BigDecimal("10000")) > 0) for production-shaped data — never trust toy values.

4. GUnit cycle for rule TDD

Gosu rules are testable without a running server. GUnit tests run in seconds and should drive every non-trivial rule change.

bash
# Run a single GUnit test class
./gradlew test --tests "com.acme.policycenter.rules.UnderwritingIssueRuleTest"

# Run all rule tests in a package, with continuous re-run on change
./gradlew test --tests "com.acme.policycenter.rules.*" --continuous

--continuous reruns the matching tests every time a file changes. Pair with the rule under test in a split editor — feedback loop drops to <5 seconds per save.

5. Sample data isolation per session

Every developer needs a deterministic fixture set, not whatever junk is in the shared dev database. Load a per-session sample at runServer start:

bash
# Load the standard sample, then a project-specific overlay
./gradlew loadSampleData -PsampleData=default -PsampleData=acme-uat-fixtures runServer

Project-specific sample sets live in modules/configuration/test/data/ and are checked in. Treat the dev database as ephemeral — never store work-in-progress data only in it; it dies on the next dropAndCreateDatabase.

Show full SKILL.md (437 more words)Show less

Output

A working local dev loop ships with all of the following:

  • gradle runServer running in dev mode with debugPort=8088 exposed; remote-debug connection attached from IntelliJ.
  • The hot-reload-vs-restart table internalized and applied — at least 80% of edits cost zero restart time.
  • A gradle test --continuous watcher running in a side terminal for GUnit-driven TDD on the current rule.
  • Sample data loaded from a checked-in fixture set, reproducible across team members.
  • A breakpoint validation habit: every non-trivial rule change is confirmed hot-reloaded by hitting a breakpoint in the new line, not by trusting Studio's reload indicator.

Examples

Example 1 — Pure rule edit, zero restart
1. Edit rule body in modules/configuration/gsrc/.../UnderwritingIssueRules.gs
2. Save (Ctrl-S)
3. Trigger the rule (issue a quote in the running PC instance)
4. Breakpoint hits the new line numbers; rule fires with new logic
5. Total time from save to confirmation: <10 seconds
Example 2 — Interface change, controlled restart
1. Modify interface in modules/configuration/gsrc/.../IPolicyCalculator.gs
2. Recognize this is in the no-hot-reload row of the table
3. Stop runServer (Ctrl-C); start ./gradlew runServer -Pdebug=true -PdebugPort=8088
4. Wait ~8 minutes; reattach debugger
5. Resume work — accept the cost rather than chasing phantom bugs from stale bytecode
Example 3 — TDD cycle on a new validation rule
bash
# Terminal 1: continuous test runner
./gradlew test --tests "com.acme.policycenter.validation.HighValueAccountValidatorTest" --continuous

# Editor: write the failing test first, watch it fail in <5s
# Implement the rule, watch the test pass in <5s
# Commit when green; do not run the full server until the rule is locked

Error Handling

SymptomCauseSolution
Code change "saved" but breakpoint fires on old line numbershot-reload silently failed (interface change, plugin registry edit)restart runServer; do not chase phantom bugs
gradle runServer hangs at Starting server for >20 minfull database rebuild from a recent schema changecheck logs in logs/PolicyCenter.log; if schema migration is running, wait it out; if hung, dropAndCreateDatabase
GUnit test passes locally, fails in CIdev database carries stale data the test depends ontests must self-fixture (@Before loads needed entities); never trust ambient sample data
IntelliJ debugger drops every few minutesrunServer crashed and auto-restarted under a launchercheck logs/PolicyCenter.log for OOM; raise -Xmx in gradle.properties
Hot reload works on Day 1, stops working after a git pullmerged change touched the plugin registry without your local picking it uprestart; rebase pulls do not always invalidate the plugin cache
ClassCastException on a class you just editedbinary-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 hitsthe rule path is not actually exercised by the test actionverify 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 maindependency cache stale./gradlew clean compileGosu (don't clean the whole project — it nukes runServer's database)

For deeper coverage (containerized dev environments, multi-developer shared servers, plugin debug logging, custom datasource hooks), see implementation guide and API reference.

See Also

  • guidewire-install-auth — once your local runServer integrates outbound to a Cloud tenant, auth layer applies the same as production
  • guidewire-sdk-patterns — when local code calls Cloud API, the same client patterns apply
  • guidewire-ci-cd-pipeline — promotion of locally-developed config through GCC slots; GUnit gates run there too
  • guidewire-core-workflow-a — PolicyCenter workflows that local dev cycles target

Resources

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/.curated/guidewire-local-dev-loop of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/API_REFERENCE.md
  • references/implementation-guide.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Guidewire Local Dev Loop next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Guidewire Local Dev Loop compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Guidewire Local Dev Loop this skilljeremylongshore/tons-of-skills-marketplace2.8k—~2.6kAutomated safety check: PassMIT
Ij Debuggerxpinjection/test-driven-spring-boot112—~6.4kAutomated safety check: PassMIT
Jest Testing PatternsChrisWiles/claude-code-showcase6.1k7 repos~1.5kAutomated safety check: PassNone
Rust TDD Workflowrtk-ai/rtk83k—~753Automated safety check: NotesApache-2.0
TDDpietheinstrengholt/rssmonster56430 repos~906Automated safety check: PassMIT
RTK Filter TDD in Rustrtk-ai/rtk83k—~1.9kAutomated safety check: NotesApache-2.0

Similar skills

  • Ij Debugger

    xpinjection/test-driven-spring-boot

    Debugger-first runtime root-cause analysis for JVM code in IntelliJ IDEA.

    112 GitHub stars~6.4k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Jest Testing Patterns

    ChrisWiles/claude-code-showcase

    Jest patterns for React Native style tests: TDD discipline, mock factory functions, module and GraphQL hook mocking, custom render helpers and anti-patterns to avoid.

    6.1k GitHub starsUsed in 7 repos~1.5k tokens
    Testing & QAAuto-check passed
  • Enforces red-green-refactor for Rust work, with idiomatic test patterns, a naming convention and a pre-commit gate of cargo fmt, clippy and test.

    83k GitHub stars~753 tokensUpdated today
    Testing & QAAuto-check: notes
  • TDD

    pietheinstrengholt/rssmonster

    Test-driven development. An agent skill from pietheinstrengholt/rssmonster.

    564 GitHub starsUsed in 30 repos~906 tokens
    Testing & QAAuto-check passed
  • Enforces red-green-refactor for new RTK output filters in Rust, using real captured fixtures, snapshot tests with insta and token-savings assertions.

    83k GitHub stars~1.9k tokensUpdated today
    Testing & QAAuto-check: notes
  • TDD Workflow

    hellangleZ/burn-in-cceverywhere-ralph

    A skill your agent uses when writing new features, fixing bugs, or refactoring code.

    112 GitHub starsUsed in 11 repos~2.4k tokens
    Testing & QAAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Guidewire Local Dev Loop

What does Guidewire Local Dev Loop do?

Iterate on Gosu rules and configuration without paying the full 5–15 minute runServer rebuild every time. Guidewire Local Dev Loop is an agent skill from jeremylongshore/tons-of-skills-marketplace. Iterate on Gosu rules and configuration without paying the full 5–15 minute runServer rebuild every time.

When should I use Guidewire Local Dev Loop?

Guidewire Local Dev Loop fits situations like: 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; building a GUnit-driven TDD cycle for rule logic.

How do I install Guidewire Local Dev Loop in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill guidewire-local-dev-loop -a claude-code`. Or copy the skill folder (skills/.curated/guidewire-local-dev-loop in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/guidewire-local-dev-loop in your project. Claude Code loads it when a task matches its description.

How do I install Guidewire Local Dev Loop in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill guidewire-local-dev-loop -a codex`. Or copy the skill folder (skills/.curated/guidewire-local-dev-loop in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/guidewire-local-dev-loop in your project. Codex loads it when a task matches its description.

Can I use Guidewire Local Dev Loop in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill guidewire-local-dev-loop -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/guidewire-local-dev-loop, .gemini/skills/guidewire-local-dev-loop, .github/skills/guidewire-local-dev-loop and .opencode/skills/guidewire-local-dev-loop in your project.

What does Guidewire Local Dev Loop need to run?

Going by SKILL.md and its folder, Guidewire Local Dev Loop needs the command-line tools its instructions call (gradle and git). Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(gradle:*), Bash(java:*), Bash(jdb:*), Grep, Glob. Compatibility (from SKILL.md): Designed for Claude Code.

Does Guidewire Local Dev Loop access the network?

SKILL.md names 4 domains. As links in the text: developer.guidewire.com, gosu-lang.github.io, docs.oracle.com and docs.gradle.org. This is read from the text; nothing was executed.

Is Guidewire Local Dev Loop safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Guidewire Local Dev Loop use?

Guidewire Local Dev Loop is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Guidewire Local Dev Loop use?

About 2.6k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.6k tokens, read only when the agent opens those files.

What are the alternatives to Guidewire Local Dev Loop?

Skills that share tags, products or a category with Guidewire Local Dev Loop: Ij Debugger (xpinjection/test-driven-spring-boot, 112 stars), Jest Testing Patterns (ChrisWiles/claude-code-showcase, 6.1k stars), Rust TDD Workflow (rtk-ai/rtk, 83k stars) and TDD (pietheinstrengholt/rssmonster, 564 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Guidewire Local Dev Loop?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.