Ghm Template Sync

Community

mattgierhart

ghm-template-sync

Detect template version drift and guide migration to the latest template version. Compares current repo against the template, identifies what's outdated, and automates safe updates while protecting product-specific content. Triggers on requests to sync with template, update template version, check for template drift, or when user asks "sync template", "update to v3", "template drift", "check template version".

Overview

Publisher	mattgierhart
Repository	`PRD-driven-context-engineering`
Skill name	`ghm-template-sync`
Stars	179
Forks	11
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by mattgierhart on GitHub. Read the source before you install it.

Installation

Install the Ghm Template Sync AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/plugins/prd-ce/skills/ghm-template-sync

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/mattgierhart/PRD-driven-context-engineering.git /tmp/PRD-driven-context-engineering
mkdir -p .claude/skills
cp -r /tmp/PRD-driven-context-engineering/plugins/prd-ce/skills/ghm-template-sync .claude/skills/ghm-template-sync

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ghm Template Sync in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ghm Template Sync on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ghm Template Sync is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Template Sync

Detect template version drift and migrate to the latest template version.

Workflow

Phase 1: Detect Current State

Read .claude/VERSION (if it exists) to get current template version
If no VERSION file, check CLAUDE.md frontmatter for template_version
If neither exists, assume v1.0.0 (pre-versioning)
Report: "Your repo is on template v{X}. Latest is v{Y}."

Phase 2: Diff Against Template

Compare your repo structure against what the current template version expects:

Check for missing files:

.claude/VERSION
.claude/domain-profile.yaml
.claude/hooks/HOOK_CONTRACT.md
.claude/hooks/context-validation.sh
.claude/hooks/context-density-gate.sh
.claude/hooks/sot-update-trigger.sh
CHANGELOG.md
MIGRATION.md

Check for stale files (should be removed):

.claude/hooks/context-validation.py
.claude/hooks/context-density-gate.py
.claude/hooks/sot-update-trigger.py
.claude/agents/HORIZON.md (replaced by subdirectory)
.claude/agents/STUDIO.md
.claude/agents/DEVLAB.md
.claude/agents/METRO.md

Check for structure issues:

settings.json: Does it use 3-level nesting? Are timeouts in seconds?
Agent directories: Do horizon/, studio/, devlab/, metro/ subdirectories exist with AGENT.md + MEMORY.md?
EPIC template: Does it use semantic headers (not numbered)?
Frontmatter: Do key files have template_version?

Phase 3: Generate Migration Plan

Output a table:

File	Status	Action	Risk
`.claude/VERSION`	Missing	Copy from template	None
`.claude/hooks/*.py`	Stale	Delete (replaced by .sh)	None
`.claude/agents/HORIZON.md`	Stale	Split into horizon/AGENT.md + MEMORY.md	Preserve MEMORY.md content
`settings.json`	Outdated	Update hook nesting + commands	Check for custom hooks
`CLAUDE.md`	Missing frontmatter	Add `template_version: "3.0.0"`	None

Phase 4: Execute Safe Updates

Auto-safe (do without asking):

Create .claude/VERSION with current template version
Add template_version frontmatter to files that lack it
Report what was done

Confirm first (show diff, ask user):

Update settings.json hook configuration
Restructure agent files (must preserve MEMORY.md)
Delete stale Python hooks
Update EPIC template headers

Never touch (product-specific):

PRD.md content (only add frontmatter)
SoT/*.md content
epics/EPIC-*.md content (only update headers on closed EPICs)
.claude/agents/*/MEMORY.md content
README.md content

Phase 5: Verify

After all changes:

Test all shell hooks produce valid JSON
Verify no Python hooks remain
Confirm settings.json uses correct nesting
Check agent subdirectories have both AGENT.md and MEMORY.md
Report summary of changes made

Version Migration Matrix

From	To	Key Changes
v1.0.0	v2.0.0	Add skills, hooks, agents, SoT standardization
v2.0.0	v3.0.0	Shell hooks, agent subdirs, semantic EPICs, versioning, domain-profile
v1.0.0	v3.0.0	All of the above (cumulative)

Safety Rules

NEVER overwrite MEMORY.md -- these contain product-specific agent memory
NEVER modify SoT content -- only add section markers or frontmatter
NEVER modify PRD.md content -- only add frontmatter version
ALWAYS show diff before destructive changes (deletes, restructures)
ALWAYS verify hooks work after updating settings.json
Commit changes incrementally -- one commit per phase, not one giant commit

Frequently asked questions

What does the Ghm Template Sync AI skill do?

Why use Ghm Template Sync on TypingMind?

Because you install it once and use it with any model. Ghm Template Sync is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ghm Template Sync in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/plugins/prd-ce/skills/ghm-template-sync. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Ghm Template Sync?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ghm Template Sync?

As many as you like. As long as a model supports skills, you can use Ghm Template Sync with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ghm Template Sync AI skill free?

Yes. It is published on GitHub by mattgierhart under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

To Tickets

mattpocock

CommunityPopular

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket…

Triage

Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.

Claude Handoff

Hand the current conversation off to a fresh background agent that picks up the work immediately.

Finishing A Development Branch

obra

CommunityPopular

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Template Sync

Workflow

Phase 1: Detect Current State

Phase 2: Diff Against Template

Phase 3: Generate Migration Plan

Phase 4: Execute Safe Updates

Phase 5: Verify

Version Migration Matrix

Safety Rules

Frequently asked questions

Related AI Skills

Set up your own AI workspace now