メニュー
Drift detection + apply for a scaffolded gemini. Re-renders the template with the same vars, computes added/removed/changed file plan, and applies with Git-style conflict markers or .rej files. Default is dry-run.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/cvsz/zagents-generator --skill upgrade-geminiコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Diff two scaffolded harnesses (ADR-031). Reports manifest meta drift + host list + per-file fingerprint changes (added/removed/changed). Exits 0 IDENTICAL, 1 DRIFT, 2 missing manifest. Use --bundle for the ADR-031 schema-1 JSON envelope.
Scaffold your own focused AI agent gemini — pick host (Claude Code, Codex, pi.dev, Hermes), template, agents, skills, and ship a npm-publishable gemini with its own npx CLI. Use when a user asks to "create my own agent gemini", "scaffold a gemini", "make a custom Claude Code plugin like ruflo", or "build a vertical AI assistant for X".
Kernel-version skew check (ADR-027). Reports manifest surface + manifest kernel + installed kernel + verdict (match/patch-diff/minor-diff/major-diff). Exits 1 on minor/major skew with a copy-pasteable `npm install @metaharness/kernel@X.Y.Z` next step. Exits 2 if no .gemini/manifest.json at path.
| name | upgrade-gemini |
| description | Drift detection + apply for a scaffolded gemini. Re-renders the template with the same vars, computes added/removed/changed file plan, and applies with Git-style conflict markers or .rej files. Default is dry-run. |
Codex skill: drift detection + apply for a scaffolded gemini.
Re-renders the template that produced the gemini against the current generator version, using the same vars the original scaffold used. Computes a 3-bucket plan:
| Bucket | Meaning |
|---|---|
| added | upstream template now has files the gemini doesn't |
| removed | upstream template no longer has files the gemini does |
| changed | upstream and gemini differ; sub-classified clean vs conflict |
A clean change means the gemini's version equals the original generation — apply safely. A conflict means the user edited the file post-scaffold; the apply step writes either Git-style inline markers or a .rej sidecar for manual merge.
/upgrade-gemini # dry-run on cwd
/upgrade-gemini path=./my-gemini
/upgrade-gemini path=./my-gemini apply=true
/upgrade-gemini path=./my-gemini apply=true conflict=rej
gemini upgrade ./my-gemini # dry-run
gemini upgrade ./my-gemini --apply # apply, inline conflicts
gemini upgrade ./my-gemini --apply --conflict=rej # apply, .rej sidecars
scaffold (create-agent-gemini)
↓
edit (you)
↓
upgrade (this skill) <- catches up to the latest template
↓
sign / verify / publish
| Code | Meaning |
|---|---|
| 0 | No drift OR clean apply (no conflicts) |
| 1 | Unresolved conflicts after apply, OR not a generated gemini, OR template missing |
| 2 | Bad --conflict= value |
CI workflows can gate on exit 1 to flag unresolved conflicts.