Skill

update-templates

Pull the latest changes from each registered upstream simulation template. Use when the user says "update templates", "pull template updates", "refresh simulators", or wants to check whether the upstream Geopol-Forecast-Council / Geopol-Forecaster repos have new commits. Reports what changed per template.

npx claudepluginhub danielrosehill/claude-code-plugins --plugin geopol-sim

Tool Access

This skill is limited to using the following tools:

BashRead

Preview

This plugin is a thin orchestrator. The actual simulator code lives in the upstream template repos and is cloned fresh by `scaffold-simulation`. This skill pulls the latest into existing workspace clones (and into a shared template-cache dir if used).

SKILL.md

Similar Skills

ui-ux-pro-max

72.7k

Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.

ui-ux-pro-max

context7-mcp

51.8k

Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.

context7-plugin

seo-cannibalization-detector

36.5k

Analyzes multiple pages for keyword overlap, SEO cannibalization risks, and content duplication. Suggests differentiation, consolidation, and resolution strategies when reviewing similar content.

antigravity-bundle-seo-specialist

Stats

Stars0

Forks0

Last CommitApr 28, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

update-templates

Update upstream templates

This plugin is a thin orchestrator. The actual simulator code lives in the upstream template repos and is cloned fresh by scaffold-simulation. This skill pulls the latest into existing workspace clones (and into a shared template-cache dir if used).

Steps

Read the registry. Load templates/registry.json.

For each template, find existing clones. Two places to check:

Workspaces — read $CLAUDE_USER_DATA/geopol-sim/config.json's registered-workspaces list (if a runstore is configured). For each workspace, check .template-id and pull only if it matches the template under consideration.
Template cache — if the plugin maintains a shared cache (default $CLAUDE_USER_DATA/geopol-sim/template-cache/<template-id>/), pull there too.

Pull each clone:

cd <clone-path>
git fetch origin <default_branch>
git log --oneline HEAD..origin/<default_branch>   # show new commits
git pull --ff-only origin <default_branch>

If the workspace has uncommitted local changes (the user edited persona briefs, for example), fall back to git stash && git pull --ff-only && git stash pop and warn the user. If the merge isn't fast-forwardable, stop for that workspace and report — don't force.

Report per-template summary:

Number of new commits pulled
One-line subject of each new commit
Workspaces that were updated vs skipped (and why)

If install_commands changed (e.g. pyproject.toml touched), suggest re-running them in each affected workspace. Don't auto-run — the user might want to inspect first.

Notes

Never rewrite git history in user workspaces. Fast-forward only.

If a workspace has gone divergent (the user committed local changes on top), report and let the user decide.

This skill does NOT update the plugin itself — that's claude plugins update geopol-sim or via Daniel's publish-plugin-update.

Update upstream templates

Steps

Read the registry. Load templates/registry.json.
For each template, find existing clones. Two places to check:
- Workspaces — read $CLAUDE_USER_DATA/geopol-sim/config.json's registered-workspaces list (if a runstore is configured). For each workspace, check .template-id and pull only if it matches the template under consideration.
- Template cache — if the plugin maintains a shared cache (default $CLAUDE_USER_DATA/geopol-sim/template-cache/<template-id>/), pull there too.
Pull each clone:
```
cd <clone-path>
git fetch origin <default_branch>
git log --oneline HEAD..origin/<default_branch>   # show new commits
git pull --ff-only origin <default_branch>
```
If the workspace has uncommitted local changes (the user edited persona briefs, for example), fall back to git stash && git pull --ff-only && git stash pop and warn the user. If the merge isn't fast-forwardable, stop for that workspace and report — don't force.
Report per-template summary:
- Number of new commits pulled
- One-line subject of each new commit
- Workspaces that were updated vs skipped (and why)
If install_commands changed (e.g. pyproject.toml touched), suggest re-running them in each affected workspace. Don't auto-run — the user might want to inspect first.

Notes

Never rewrite git history in user workspaces. Fast-forward only.
If a workspace has gone divergent (the user committed local changes on top), report and let the user decide.
This skill does NOT update the plugin itself — that's claude plugins update geopol-sim or via Daniel's publish-plugin-update.