[gold-silver-copper]

meta init claude wrote each skill as a flat .claude/skills/meta-*.md file. Claude Code only loads skills from .claude/skills/<name>/SKILL.md with name/description frontmatter, so none of the six meta skills were ever loaded (in harmony, Claude's skill list has no meta-* entries). The worktree skill also used a command that doesn't exist (meta worktree) and told agents to skip worktrees for quick fixes.

What changes

Install layout (src/init.rs)

• The skill sources move to .claude/skills/meta-<name>/SKILL.md with frontmatter (descriptions from gitkb/meta's claude-plugin/skills). They are embedded with a small skill! macro and installed at the same path.
• With --update or --force, the old flat meta-<name>.md each folder replaces is deleted, so re-running in an existing repo leaves one copy. Plain meta init claude skips existing files, so it leaves them alone. Only those six filenames are touched; other files in .claude/skills/ stay.

Before / after in a repo:

.claude/skills/meta-git.md            ->  .claude/skills/meta-git/SKILL.md

meta init claude --help (src/main.rs) ran the full install, including registering the gitkb/claude-plugins marketplace in the user's global Claude settings. It now only prints the init help.

Skill text, checked against meta … --help and the source of meta_cli, meta_git_cli, meta_git_lib, meta_project_cli and loop_lib:

• meta-worktree: rewritten. meta git worktree … everywhere, remove (not destroy), positional commit-ish (not --from-ref), --no-deps/--recursive/--dry-run/--strict, list [<name>] --metadata-only. "Skip worktrees for quick single-file fixes" is replaced by: every change gets a worktree; read-only work may stay in the primary checkout. Also corrected: --ttl (not --ephemeral) is what prune acts on, remove refuses dirty repos without --force, post-destroy hook runs on remove. --from-pr never applies to the root repo and only warns when nothing matches, so the old GitHub Actions example could pass on unchanged code: it is removed, and the skill gives a root-PR recipe instead (git fetch origin <b>:<b>, then create <name> --repo .:<b> --repo <child> --strict; tried in a scratch repo with and without an existing local branch, and prune --dry-run leaves it alone: a set holding only the root repo is "orphaned" to prune, which force-removes it). diff --stat is a no-op (diff always prints a stat summary of committed changes). Worktree commands must run from the primary checkout; context detection and worktree exec skip repos nested inside another repo of the set; --include/--exclude match the absolute path, which contains the set name.
• meta-safety: meta --strict git worktree …; --strict covers worktree checks only and doesn't roll back; removed --ordered (no such flag; dependency order comes from the MCP tool meta_execution_order).
• meta-exec: with meta-rust installed every meta exec -- cargo … goes to it (only build/test work); parallel is the default (--sequential exists); --silent hides errors too; include/exclude are substring matches on paths; meta --exclude X exec -- cargo update (the old example passed --exclude to cargo); meta --primary exec; removed --ordered.
• meta-git: meta git update only clones missing repos (pull with meta git pull); commit commits staged changes; snapshot restore stashes tracked changes only and asks to confirm without --force; removed meta git setup-ssh (it's a pass-through to a git command that doesn't exist).
• meta-plugins: no meta project sync (use meta git update); plugin discovery is .meta/plugins/ and ~/.meta/plugins/; Rust plugin only if installed.
• meta-workspace: meta project list --recursive --json, "every repo at this level" instead of "ALL repos", meta git clone --depth is shallow depth (--meta-depth limits recursion).

Verification

• cargo fmt --check, cargo clippy --all-targets -D warnings, and the init:: unit tests (10, incl. new test_update_replaces_flat_skill_files and test_default_install_keeps_flat_skill_files) pass locally.
• Scratch meta repo, this build, PATH without claude:
  • meta init claude --help → prints help, creates nothing.
  • meta init claude → six .claude/skills/meta-*/SKILL.md + rules + settings.
  • meta init claude --update over the six flat files plus a custom.md → only folders remain, custom.md kept.
• Fresh claude -p (no tools) asked to list skills starting with meta-: lists all six in both scratch repos; in a repo with the old flat files: NONE.

Notes

• Not changed here (CLI behavior, other repos): meta git update --help says it pulls existing repos but only clones missing ones; --from-pr ignores the root repo; context detection skips nested set members; diff --stat is accepted but unused; prune treats a root-only set as orphaned. The skills describe current behavior. The two installed rule files (.claude/rules/meta-*.md) also have small inaccuracies (meta git snapshot restore without --force prompts; meta git commit commits staged changes, not "all dirty repos"; --include is a substring match); left for a follow-up so the rules and their gitkb/meta copies change together.
• Companion PRs: fix(skills): copy Claude skills from meta_cli and test the new layout meta#102 (single source + tests/init.bats; same branch name, so its CI builds this branch) and gitkb/harmony#154 (worktree policy in AGENTS.md). Harmony needs a meta release with this change, then meta init claude --update.

Task: tasks/harmony-2708

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 2d929bd3-272a-4a05-bd9f-bf3c59e9a465

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}