template-upgrade
Skill4 starsChanged 6 months agoMITView on GitHub
Upgrade a project that is based on the agentic-mobile-blueprint template. Use when the user asks to check for template updates, upgrade to a newer version, or apply template changes.
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- vbonk/repo-templatetheir own version, first seen Aug 6, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- vbonk/repo-template★ 8same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- apple-appstore-setupSkill
- eas-mobile-deploymentSkill
- edge-functionsSkill
- frontend-developmentSkill
- google-play-setupSkill
- langfuse-tracingSkill
- mobile-developmentSkill
- posthog-analyticsSkill
- push-notificationsSkill
- revenuecatSkill
- sentry-integrationSkill
- social-auth-setupSkill
- stripe-paymentsSkill
- supabase-email-templatesSkill
- template-releaseSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Read the local version:
- Distinctive: line 30
If local == latest: nothing to do.
- Distinctive: line 54
Read the full file before applying anything.
- Distinctive: line 67
Only touch files listed in the upgrade notes.
- Very specific: line 72
Never touch mobile/app/, example screens, or maestro/ flows — these are owned by the consuming project.
- Distinctive: line 78
After applying all changes:
- Distinctive: line 96
If the user just wants to see what would change without applying it:
- Distinctive: line 100
Ask the user which versions or sections to apply.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Template Upgrade
This project is based on agentic-mobile-blueprint.
Template releases publish upgrade notes to .agents/skills/template-upgrade/vX.Y.Z.md.
Each file documents only shared infrastructure changes — skills, _shared/ utilities, build config, env vars, deps.
App scaffold files (mobile/app/, example screens) are intentionally excluded.
Step 1 — Check for updates
Read the local version:
cat TEMPLATE_VERSIONFetch the template's latest version:
https://raw.githubusercontent.com/Ampli-Group/agentic-mobile-blueprint/main/TEMPLATE_VERSIONIf local == latest: nothing to do. Stop here and tell the user they are up to date.
Step 2 — Discover upgrade notes to apply
Fetch the list of upgrade files from the template:
https://api.github.com/repos/Ampli-Group/agentic-mobile-blueprint/contents/.agents/skills/template-upgradeThis returns a JSON array. Filter for files whose name matches vX.Y.Z.md and whose version is strictly greater than the local version and less than or equal to the latest version. Sort them in ascending semver order (oldest first).
Semver comparison: parse each version as [MAJOR, MINOR, PATCH] integers and compare numerically — do not do lexicographic string comparison.
Example: local = 0.1.0, latest = 0.3.1 → apply v0.1.1.md, v0.2.0.md, v0.3.0.md, v0.3.1.md in that order (only files that actually exist).
Step 3 — Fetch and read each upgrade file
For each file to apply, fetch its content:
https://raw.githubusercontent.com/Ampli-Group/agentic-mobile-blueprint/main/.agents/skills/template-upgrade/vX.Y.Z.mdRead the full file before applying anything. Build a complete picture of all changes across all versions first.
Step 4 — Apply changes
Work through the upgrade notes in version order. For each version:
- Breaking Changes — apply these first and confirm with the user if they are destructive.
- New Features / Improvements — copy or adapt shared files as described.
- Bug Fixes — apply targeted fixes to shared code.
- Dependency Updates — update
package.json,deno.json, or relevant config files.
Key rules while applying:
- Only touch files listed in the upgrade notes. Do not infer other changes.
- For shared utilities (
supabase/functions/_shared/), copy the change directly — these files are not expected to be customised by consuming projects. - For skills (
.agents/skills/), merge carefully — the project may have added its own skills. - For
AGENTS.md, apply the described changes as a patch rather than overwriting — the project will have customised it. - For env vars: add new entries to
.env.localfiles and remind the user to fill them in. Runmise run configureif the upgrade notes say to. - Never touch
mobile/app/, example screens, ormaestro/flows — these are owned by the consuming project. - Never copy
.agents/skills/template-upgrade/vX.Y.Z.mdfiles into the project. These release notes live only in the blueprint repo. Fetch and read them from GitHub; do not write them to disk. - Never copy
.agents/skills/template-release/into the project. The release skill is for cutting blueprint releases — it has no use in a consuming project.
Step 5 — Bump local TEMPLATE_VERSION
After applying all changes:
echo "X.Y.Z" > TEMPLATE_VERSIONStep 6 — Report
Summarise:
- What versions were applied
- What files were changed
- Any manual steps the user still needs to take (e.g. fill in new env vars, review a merged conflict)
- Anything skipped and why
Shortcut — check only, no apply
If the user just wants to see what would change without applying it:
- Follow Steps 1–3 only.
- Print a summary of each version's changes.
- Ask the user which versions or sections to apply.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

