upgrade
Skill7 starsChanged 6 months agoMITView on GitHub
Run goc upgrade, then drive LLM reconciliation of evolving .game-of-cards/ files from the engine's divergence report, preserving user-owned content. AUTO-INVOKE on "upgrade goc", "run goc upgrade", "sync goc templates".
32 other projects use a version of this.
Adopted by
Most recently taken up by
- Robo-Co-op/robobuilder-standardtheir own version, first seen Nov 16, 2026
- jianghailong-xy/orbittheir own version, first seen Nov 15, 2026
- link7373/agentic-bi-teamtheir own version, first seen Nov 10, 2026
- Mrbaeksang/skillstheir own version, first seen Nov 8, 2026
- roedyrustam/doku-gemini-mcptheir own version, first seen Nov 8, 2026
- aminbadh/workspace-startertheir own version, first seen Nov 1, 2026
Used with
Projects with it also use new, context and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
codebycoreySkillnew
Start a new change with a proposal. Use when starting a feature, creating a proposal, or beginning planned work.
Also in 4 projects that use this
aegiswizardSkillcontext
Also in 3 projects that use this
MicrosoftSkillinit
Also in 6 projects that use this
AnthropicSkillstatus
Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.
Also in 5 projects that use this
tuistSkillmigrate
Migrates existing Xcode projects to Tuist generated workspaces with build and run validation, external dependency mapping, and migration checklists. Use when adopting Tuist for an existing app or converting a hand-edited Xcode project to generated projects.
Also in 3 projects that use this
imehrSkillfrontend
Use when building UI components, pages, or features - guides Claude through the approved frontend stack (Next.js 15, React 19, Shadcn, Tailwind) with design-first workflow for complex UIs, enforcing patterns and quality standards
Also in 3 projects that use this
Other versions32 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 32
- langwatch/langwatch★ 5ksame name
- agenticnotetaking/arscontexta★ 3.5ksame name
- heyitsnoah/claudesidian★ 2.6ksame name
- TokenRollAI/cc-plugin★ 483same name
- dcb/homeassistant-claude-kit★ 125same name
- rust-off-rails/rustoffrails★ 49same name
- rvdbreemen/adr-kit★ 13same name
- jamillazarev/multica-ops★ 11same name
- ivankuznetsov/llm-wiki★ 9same name
- jianghailong-xy/orbit★ 7same name
22 more not listed
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 repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- site/llms.txtllms.txt
- advance-cardSkill
- audit-deckSkill
- card-schemaSkill
- claude-kickoffSkill
- create-cardSkill
- decide-cardSkill
- deckSkill
- finish-cardSkill
- kickoffSkill
- next-cardSkill
- pull-cardSkill
- refine-deckSkill
- retrospectiveSkill
- scan-deckSkill
- standupSkill
- tune-cadenceSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 4 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 26 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
If the engine has preserved a *diverged* copy of either, the engine itself has nothing to say about whether real upstream changes need to …
- Very specific: line 79
When the user approves, write the merged content back to .game-of-cards/<path> directly.
- Distinctive: line 83
If the local file and template are obviously compatible (e.g., local added a new top-level key the template doesn't know about, and the …
- Very specific: line 112
Commit follows repo policy: If the reconciliation pass modified any files, the user typically wants those staged alongside the engine's own …
- Very specific: line 143
Does NOT re-run goc upgrade.
- Distinctive: line 147
Does NOT overwrite user-owned content stubs or workflow hooks.
- Distinctive: line 151
Does NOT touch the AGENTS.md / CLAUDE.md GoC marker block.
- Very specific: line 154
Does NOT bisect or git revert the engine's writes.
“Common” is measured: kept by at least 6 in 10 of the 26 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
When to invoke
Invoke when the user says "upgrade goc", "pull the latest goc", "sync goc templates", "run goc upgrade", or asks how to upgrade the GoC version in this repo. The engine's safety guarantee — never overwrite authored project state — holds with or without this skill; the skill exists to reconcile evolving upstream content into the local copy where the engine's "preserve" verdict alone leaves real upstream changes on the floor.
Upgrade GoC
goc upgrade is deterministic and safe by construction — it never
overwrites authored content under .game-of-cards/. That guarantee
holds for every consumer regardless of whether an agent is present
(headless CI runs, scheduled cron, scripted upgrades).
But "never overwrite" is not the same as "stay current". Two files
under .game-of-cards/ ship real, evolving content that the upstream
template may have changed across versions:
README.md— the hook-point catalogue documenting which content stubs and workflow hooks the skills consume, and where.config.yaml— the runtime-neutral closure attestation config (layer_2_project_dod,layer_3_goc_dod) plus workflow options.
If the engine has preserved a diverged copy of either, the engine itself has nothing to say about whether real upstream changes need to land in the consumer's local copy. That is this skill's job.
For the 12 user-owned content stubs and workflow hooks, the engine's "preserved" verdict is the whole story — the templates ship blank by design, so there is nothing to reconcile. This skill confirms that to the user so they know nothing was lost.
For the AGENTS.md / CLAUDE.md GoC marker block, the engine
regenerates the goc-owned region wholesale via the marker-bounded
merge (<!-- BEGIN GOC vX.Y.Z --> … <!-- END GOC -->). That region
is goc-owned, not user-owned, so nothing to reconcile — this skill
summarizes what methodology guidance changed across the upgrade so
the user knows what new behavior the agents will now follow.
Workflow
Run
goc upgradeand capture stdout. The engine emits a sentinel-marked JSON divergence report after its normal upgrade output. Plaingoc upgradeis the whole invocation: the report follows on every run, including one that answersalready at goc X — nothing to do.because the version is already current (someone rangoc upgradein a terminal first, or an earlier session stopped after this step). A diverged file gives the engine nothing to write, but it is still in the report:GoC project-state divergence report (JSON): {"version": 1, "templates_root": "...", "files": [...]}Parse the JSON on the line immediately following the marker. Each entry has
path(relative to.game-of-cards/),status(create/unchanged/preserved), andownership(user-owned/evolving).For each
evolvingfile withstatus: preserved— read the local file at.game-of-cards/<path>AND the shipped template at<templates_root>/<path>. Drive a 2-way reconcile:- Diff the two files mentally. Identify what changed upstream (lines present in the template that are absent or different in the local copy).
- For each upstream change, decide whether it should land:
- Mechanical updates (new key with default value, new
comment, new doc paragraph that does not contradict local
customization) → propose the merged content and
AskUserQuestionfor confirmation. - Conflicting with the user's customization → describe both sides and ask the user how to resolve. Default to keeping the user's value; surface the upstream change as informational.
- Mechanical updates (new key with default value, new
comment, new doc paragraph that does not contradict local
customization) → propose the merged content and
- When the user approves, write the merged content back to
.game-of-cards/<path>directly. Do not invokegoc upgradeagain — the engine has already done its work; this is a one-shot reconciliation. - If the local file and template are obviously compatible (e.g., local added a new top-level key the template doesn't know about, and the template added an unrelated comment), apply both sides and report the merged result.
- For each
user-ownedfile withstatus: preserved— confirm to the user, in one line per file: "kept your<path>(nothing upstream)". The shipped template is permanently blank by design, so there is no upstream content to bring across. The confirmation exists so the user does not have to wonder whether the upgrade silently overwrote anything. - For files with
status: create— these are absent locally and were scaffolded by the engine. Mention them so the user knows new files appeared (e.g., a new workflow-hook stub for a skill that landed in this version). - For files with
status: unchanged— silent. The local copy already matches the template; nothing to report. - Summarize AGENTS.md / CLAUDE.md GoC block changes. Diff the
<!-- BEGIN GOC vX.Y.Z -->…<!-- END GOC -->region before and after the upgrade (the engine already rewrote it;git diffon the working tree surfaces the delta), and present a short list of substantive methodology changes — new verbs documented, new conventions enforced, behavioral defaults flipped. This is informational, not a merge — the marker-bounded region is goc-owned and the upgrade contract is that it gets regenerated. - Commit follows repo policy. If the reconciliation pass
modified any files, the user typically wants those staged
alongside the engine's own changes (the bumped
.goc-version, the rewritten methodology block, any newly-scaffolded files). The engine'sgoc upgradedoes NOT auto-commit; commit the union of engine writes + reconciliation edits with a subject likechore(goc): upgrade to vX.Y.Z.
Why the engine is safe without this skill
The engine's _sync_game_of_cards_config classifies every shipped
file against the on-disk copy and only writes when the destination is
absent. Diverged files are preserved unconditionally — no prompt, no
confirmation, no agent in the loop. This means:
- A scripted upgrade in CI does not lose authored content.
- A scheduled cron
goc upgradedoes not lose authored content. - A user running
goc upgradein a terminal without invoking this skill does not lose authored content.
What the user loses without this skill is informational reconciliation
of upstream changes to the two evolving files. The local copies stay
exactly as the user left them; the upstream changes sit in the
template payload until the next time someone runs this skill (or
manually diffs .game-of-cards/README.md against
<templates_root>/README.md). That holds after the version is
already current too, because the engine's no-op run still prints
the report.
What this skill does NOT do
- Does NOT re-run
goc upgrade. The engine has already done its work by the time this skill is reading the report. Re-running would write nothing (version is now current) and print the same report again. - Does NOT overwrite user-owned content stubs or workflow hooks. The templates are blank by design — there is nothing upstream to bring across, so the reconcile pass for those files is purely a confirmation.
- Does NOT touch the
AGENTS.md/CLAUDE.mdGoC marker block. The engine regenerates that region wholesale on every upgrade; the contract is "do not edit between the markers." - Does NOT bisect or
git revertthe engine's writes. If the reconciliation pass produces a result the user dislikes, the user edits the file by hand or invokesSkill(create-card)to file the disagreement as a card for follow-up.
Cross-references
Skill(kickoff)— first-time setup in a fresh repo. The kickoff skill writes the initial.game-of-cards/scaffold; this skill is the follow-up that runs every time the user wants to pull a new goc version into an existing repo.Skill(card-schema)— frontmatter and DoD conventions the upgraded engine may have evolved.Skill(deck)— the methodology surface the regenerated AGENTS.md / CLAUDE.md block documents.
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.

