guild-cli 0.2.0__tar.gz → 0.4.0__tar.gz

guild_cli-0.4.0/.claude/skills/agent-config/SKILL.md

@@ -0,0 +1,82 @@
+---
+name: agent-config
+description: >
+  Show a Culture agent's full configuration in one read-only view: its
+  system-prompt file (CLAUDE.md / AGENTS.md / GEMINI.md), the parallel
+  culture.yaml, and the agent's local .claude/skills index. Use when an
+  operator says "show agent <name>", "what does <agent> look like", or before
+  teaching/onboarding an agent and you need to see its current kit + config.
+  Backs the `guild show` verb. Vendored from steward (cite-don't-import);
+  inventory only — it reports, it does not judge alignment or drift.
+type: command
+---
+
+# agent-config — surface a Culture agent's config in one view
+
+guildmaster is the mesh's skills supplier and owns the **inventory** surfaces:
+"what kit + config does this agent have?" This skill answers exactly that for a
+single agent, showing the three artifacts that together define it:
+
+1. **System-prompt file** (`CLAUDE.md` / `AGENTS.md` / `GEMINI.md`) — the
+   prompt-side guidance for the agent's backend. The script detects which file
+   is present from a backend-fingerprint registry.
+2. **`culture.yaml`** — the runtime-side config (`agents:` list with `suffix`,
+   `backend`, `model`, `system_prompt`, `channels`, `tags`, `acp_command`,
+   `extras`). Lives parallel to the prompt file at the project root.
+3. **`.claude/skills/*/SKILL.md`** — the per-project skills the agent can
+   invoke, one line each (name + truncated description).
+
+This is the **inventory half** of the steward → guildmaster split
+([issue #12](https://github.com/agentculture/guildmaster/issues/12)): it reports
+the config, it does **not** interpret drift or judge alignment. The relationship
+graph and the "is this agent aligned?" judgment stay with `steward overview` /
+`steward doctor`.
+
+## When to use
+
+- Before `guild teach` / `guild onboard` — see an agent's current kit + config.
+- When an operator asks "show me agent `<name>`" or "what does `<agent>` run".
+- Read it, don't guess — before answering a question about what an agent does.
+
+## How to run
+
+One script, two ways to call it (or just run `guild show`, which wraps it):
+
+```bash
+# Path mode — point at any directory with a prompt file + culture.yaml
+.claude/skills/agent-config/scripts/show.sh ../culture
+
+# Suffix mode — resolve a registered agent suffix via the Culture server's
+# manifest (location set by culture_server_yaml in skills.local.yaml)
+.claude/skills/agent-config/scripts/show.sh daria
+```
+
+Output is three sections: the detected system-prompt file, `culture.yaml` (or
+`(missing)`), and a one-line summary per local skill (name + description,
+truncated to 120 chars).
+
+## What to look at in `culture.yaml`
+
+| Field | Why it matters |
+|-------|----------------|
+| `suffix` | Identifies the agent on the mesh. |
+| `backend` | One of `claude` / `codex` / `copilot` / `acp`. The all-backends rule means a feature in one must land in all four. |
+| `model` | Drift here changes behavior silently. |
+| `system_prompt` | Should not contradict the prompt file. |
+| `channels` | Where the agent listens. |
+| `tags`, `extras`, `acp_command` | Backend-specific. |
+
+## Notes
+
+- **Read-only.** The script never edits agent files. It reports; it does not
+  flag or fix drift — that judgment is steward's lane.
+- **Backend-aware.** Prompt-file detection comes from
+  `data/backend-fingerprints.yaml` (the `prompt:` mapping), falling back to the
+  built-in `(CLAUDE.md AGENTS.md GEMINI.md)` list if the registry is absent.
+- **Per-machine config.** Suffix mode reads `culture_server_yaml` from
+  `.claude/skills.local.yaml` (git-ignored), falling back to
+  `.claude/skills.local.yaml.example`.
+- **Vendored from steward** (`agent-config`). guildmaster owns this copy and may
+  diverge; re-sync from steward's canonical copy when it changes. Divergences:
+  the SKILL.md is reframed for guildmaster's inventory role and adds
+  `type: command` for the culture backend's skill loader.

guild_cli-0.4.0/.claude/skills/agent-config/data/backend-fingerprints.yaml

@@ -0,0 +1,30 @@
+# Canonical backend fingerprint registry. Vendored from steward's agent-config
+# skill (cite-don't-import); guildmaster owns this copy. Read by the agent-config
+# show.sh (bash), which `guild show` shells out to. Upstream steward also reads
+# it from a Python detector; guildmaster has no parallel detector, so only the
+# `backends:` prompt mapping below is load-bearing here. Keep that mapping in
+# sync with upstream when re-syncing.
+#
+# `prompt`        — the backend's system-prompt filename at the repo root.
+# `steering`      — files/dirs distinctive enough to attribute to this backend.
+# `shared_steering` — files/dirs that belong to NO specific backend. A repo
+#                   declared as any backend may have these without triggering a
+#                   mismatch. `.agents` is a generic Culture agent-config
+#                   convention. `.claude/settings.json` and
+#                   `.claude/settings.local.json` are generic Claude Code
+#                   (editor/CLI) workspace config files — they appear in any
+#                   repo that uses Claude Code as the development tool,
+#                   regardless of the agent backend, so they must never be used
+#                   to infer the backend or flag a mismatch. The claude backend
+#                   is identified solely by its `CLAUDE.md` prompt file.
+#                   `.github/copilot-instructions.md` is generic GitHub Copilot
+#                   editor/IDE config — any repo may have it regardless of the
+#                   declared agent backend, so it must not trigger a mismatch.
+backends:
+  claude:  { prompt: CLAUDE.md, steering: [] }
+  codex:   { prompt: AGENTS.md, steering: [".codex"] }
+  acp:     { prompt: AGENTS.md, steering: [".kiro"] }
+  copilot: { prompt: AGENTS.md, steering: [] }
+  gemini:  { prompt: GEMINI.md, steering: [".gemini"] }
+shared_steering: [".agents", ".claude/settings.json", ".claude/settings.local.json", ".github/copilot-instructions.md"]
+prompt_fallback: AGENTS.md

guild_cli-0.4.0/.claude/skills/agent-config/scripts/show.sh

@@ -0,0 +1,136 @@
+#!/usr/bin/env bash
+set -euo pipefail
+# Show a Culture agent's full configuration in one view:
+# the detected system-prompt file (CLAUDE.md / AGENTS.md / GEMINI.md), the
+# parallel culture.yaml, and the .claude/skills/ index.
+#
+# Usage: show.sh <path-or-agent-suffix>
+#
+# Path mode:   show.sh ../culture
+# Suffix mode: show.sh daria   (resolved via culture_server_yaml in skills.local.yaml)
+#
+# Exit codes:
+#   0   success
+#   1   environment error (missing manifest, missing PyYAML for suffix mode)
+#   2   user error (no target given, unknown suffix, target path doesn't exist)
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+SKILL_DIR="$(cd "$SCRIPT_DIR/.." && pwd)"
+REPO_ROOT="$(cd "$SKILL_DIR/../../.." && pwd)"
+
+CFG="$REPO_ROOT/.claude/skills.local.yaml"
+[ -f "$CFG" ] || CFG="$REPO_ROOT/.claude/skills.local.yaml.example"
+
+# Read a top-level YAML scalar from CFG. Schema is intentionally tiny:
+#   key: value     (with optional surrounding quotes / trailing comment)
+# No PyYAML dependency.
+read_cfg() {
+    awk -v key="$1" '
+        $0 ~ ("^" key ":[[:space:]]*") {
+            sub("^" key ":[[:space:]]*", "")
+            sub(/[[:space:]]*#.*$/, "")
+            sub(/^[[:space:]]+/, ""); sub(/[[:space:]]+$/, "")
+            sub(/^["\047]/, ""); sub(/["\047]$/, "")
+            print
+            exit
+        }
+    ' "$CFG"
+}
+
+target="${1:-}"
+if [ -z "$target" ]; then
+    echo "Usage: $(basename "$0") <path-or-agent-suffix>" >&2
+    exit 2
+fi
+
+if [ -d "$target" ]; then
+    DIR="$target"
+else
+    SERVER_YAML_RAW="$(read_cfg culture_server_yaml)"
+    SERVER_YAML="${SERVER_YAML_RAW/#\~/$HOME}"
+    if [ ! -f "$SERVER_YAML" ]; then
+        echo "no server manifest at $SERVER_YAML — set culture_server_yaml in $CFG" >&2
+        echo "or pass an explicit path instead of suffix '$target'" >&2
+        exit 1
+    fi
+    # Suffix mode parses Culture's server manifest, whose schema is dictated by
+    # Culture (not by us) and includes nested mappings — too rich for awk.
+    # We use python+PyYAML here, with a friendly install hint if it's missing.
+    if ! python3 -c 'import yaml' 2>/dev/null; then
+        echo "suffix mode needs Python + PyYAML to parse $SERVER_YAML" >&2
+        echo "  install: pip install --user pyyaml   (or: uv pip install pyyaml)" >&2
+        echo "  or pass an explicit path instead of suffix '$target'" >&2
+        exit 1
+    fi
+    # Use a dedicated exit code (2) for "unknown suffix" so the steward CLI
+    # wrapper can distinguish user errors (typo'd suffix) from env errors
+    # (missing manifest / PyYAML).
+    if ! DIR=$(python3 - "$SERVER_YAML" "$target" <<'PY'
+import sys, yaml, pathlib
+manifest_path, suffix = sys.argv[1], sys.argv[2]
+m = yaml.safe_load(pathlib.Path(manifest_path).read_text()) or {}
+agents = m.get('agents', {})
+entry = agents.get(suffix)
+if entry is None:
+    print(f"no agent registered with suffix {suffix!r} in {manifest_path}", file=sys.stderr)
+    sys.exit(2)
+print(entry['directory'] if isinstance(entry, dict) else entry)
+PY
+); then
+        exit 2
+    fi
+fi
+
+DIR="${DIR/#\~/$HOME}"
+
+# Recognized prompt filenames come from the shared registry (single source
+# of truth with the Python detector). Fall back to the built-in list if the
+# registry isn't present (e.g. skill vendored without the data file).
+REGISTRY="$SKILL_DIR/data/backend-fingerprints.yaml"
+prompt_files=()
+if [ -f "$REGISTRY" ]; then
+    while IFS= read -r pf; do
+        [ -n "$pf" ] && prompt_files+=("$pf")
+    done < <(grep -oE 'prompt:[[:space:]]*[^,}[:space:]]+' "$REGISTRY" | awk '{print $NF}' | sort -u)
+fi
+[ ${#prompt_files[@]} -eq 0 ] && prompt_files=(CLAUDE.md AGENTS.md GEMINI.md)
+
+shown=0
+for pf in "${prompt_files[@]}"; do
+    if [ -f "$DIR/$pf" ]; then
+        echo "=== $DIR/$pf ==="
+        cat "$DIR/$pf"
+        echo
+        shown=1
+    fi
+done
+if [ "$shown" -eq 0 ]; then
+    echo "=== $DIR (system prompt) ==="
+    echo "(no recognized prompt file: ${prompt_files[*]})"
+    echo
+fi
+echo "=== $DIR/culture.yaml ==="
+if [ -f "$DIR/culture.yaml" ]; then cat "$DIR/culture.yaml"; else echo "(missing)"; fi
+echo
+echo "=== $DIR/.claude/skills/ ==="
+found=0
+for s in "$DIR"/.claude/skills/*/SKILL.md; do
+    [ -f "$s" ] || continue
+    found=1
+    name=$(awk '/^name:/{print $2; exit}' "$s")
+    desc=$(awk '
+        /^description:/ {
+            sub(/^description:[[:space:]]*/, "")
+            buf = $0
+            flag = 1
+            next
+        }
+        flag && /^[a-z_-]+:/ { flag = 0 }
+        flag { buf = buf " " $0 }
+        END { gsub(/^[[:space:]]+|[[:space:]]+$/, "", buf); print buf }
+    ' "$s")
+    printf "  %-30s %s\n" "$name" "${desc:0:120}"
+done
+if [ "$found" -eq 0 ]; then
+    echo "  (no skills)"
+fi

guild_cli-0.4.0/.claude/skills/onboard/SKILL.md

@@ -0,0 +1,40 @@
+---
+name: onboard
+description: Onboard a brand-new sibling agent into the AgentCulture mesh — guildmaster's new-agent ceremony for supplier operators. Files ONE consolidated issue (full canonical kit as per-skill sections + an identity-setup section), registers the agent in the ledger, and records the pins it should vendor. Dry-run by default; --apply files. Use when an operator says "onboard a new agent/sibling" or "welcome a new repo to the mesh".
+type: command
+---
+
+# onboard — welcome a brand-new sibling agent
+
+`onboard` is guildmaster's new-agent ceremony, for **supplier operators**
+bringing a brand-new **sibling repo** into the mesh. It wraps the
+`guild onboard` CLI verb.
+
+It is `teach` of the **whole canonical kit** in new framing, plus the
+new-agent bookkeeping:
+
+- one consolidated GitHub issue — every canonical skill as a per-skill section
+  (inbound skills, e.g. the devague trio, carry an origin-attribution block) —
+  followed by an **identity-setup section** (culture.yaml + backend + prompt
+  file, so the sibling passes `steward doctor`);
+- **ledger registration** — the agent is added to `docs/skill-sources.md` as a
+  downstream consumer of every canonical skill (idempotent);
+- a **verification record** — the pins the sibling is expected to vendor.
+
+**Dry-run by default**: it renders the issue, the ledger diff it *would* apply,
+and the verification record — writing nothing. `--apply` files the issue, writes
+the ledger, and records the pins. Going live is gated on the steward→guildmaster
+cutover (`docs/cutover.md`).
+
+## How to run
+
+```bash
+# Render the full onboarding ceremony (dry-run):
+bash .claude/skills/onboard/scripts/onboard.sh --agent agentculture/newsib
+
+# Commit it — file the issue, write the ledger, record the pins:
+bash .claude/skills/onboard/scripts/onboard.sh --agent agentculture/newsib --apply
+```
+
+A bare `--agent` name gets the `--org` prefix (default `agentculture`).
+`--json` emits a structured payload.

guild_cli-0.4.0/.claude/skills/onboard/scripts/onboard.sh

@@ -0,0 +1,17 @@
+#!/usr/bin/env bash
+set -euo pipefail
+# onboard — forward to `guild onboard`, resolving the CLI portably.
+#
+# Prefers an installed `guild` on PATH (the normal case), falling back to
+# `uv run guild` inside a source checkout. Every argument is forwarded verbatim.
+# Dry-run is the CLI's default; pass --apply to file the issue + write the
+# ledger + record the pins.
+
+if command -v guild >/dev/null 2>&1; then
+    exec guild onboard "$@"
+elif command -v uv >/dev/null 2>&1; then
+    exec uv run guild onboard "$@"
+fi
+
+echo "guild not found on PATH. Install it: uv tool install guild-cli" >&2
+exit 2

guild_cli-0.4.0/.claude/skills/teach/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: teach
+description: Teach a set of skills to a set of AgentCulture mesh agents — guildmaster's supplier verb for operators propagating skills to sibling agents. Files one agent-major GitHub issue per target (per-skill sections bundled), new-vs-resync auto-detected from the ledger. Dry-run by default; --apply files. Use when an operator says "teach these skills to those agents", "broadcast a skill update", or "resync vendored skills".
+type: command
+---
+
+# teach — propagate a set of skills to a set of mesh agents
+
+`teach` is guildmaster's supplier verb. The audience is **supplier operators**
+(guildmaster itself; steward during the transition) targeting **sibling repos**
+in the mesh. It wraps the `guild teach` CLI verb.
+
+It is **agent-major**: one GitHub issue per target agent, bundling a per-skill
+*section* for every skill that agent receives — not one issue per skill.
+New-vs-resync framing is auto-detected per `(skill, agent)` from
+`docs/skill-sources.md`. **Dry-run by default**; pass `--apply` to file the
+issues. Going live is gated on the steward→guildmaster cutover (`docs/cutover.md`).
+
+## How to run
+
+```bash
+# Render (dry-run) — what would be filed, nothing posted:
+bash .claude/skills/teach/scripts/teach.sh --skill cicd --skill communicate --to tipalti
+
+# Teach the full canonical kit to two agents and file the issues:
+bash .claude/skills/teach/scripts/teach.sh --all --to daria --to tipalti --apply
+```
+
+Skills must be selected explicitly (`--skill`, repeatable, or `--all`) — there
+is no implicit default. Targets come from `--to` (bare names get `--org`,
+default `agentculture`), falling back to the ledger's current consumers per
+skill when `--to` is omitted. `--json` emits a structured payload.

guild_cli-0.4.0/.claude/skills/teach/scripts/teach.sh

@@ -0,0 +1,17 @@
+#!/usr/bin/env bash
+set -euo pipefail
+# teach — forward to `guild teach`, resolving the CLI portably.
+#
+# Prefers an installed `guild` on PATH (the normal case), falling back to
+# `uv run guild` inside a source checkout. Every argument is forwarded verbatim,
+# so this wrapper exists only for portable resolution + discoverability as a
+# skill. Dry-run is the CLI's default; pass --apply to file issues.
+
+if command -v guild >/dev/null 2>&1; then
+    exec guild teach "$@"
+elif command -v uv >/dev/null 2>&1; then
+    exec uv run guild teach "$@"
+fi
+
+echo "guild not found on PATH. Install it: uv tool install guild-cli" >&2
+exit 2

{guild_cli-0.2.0 → guild_cli-0.4.0}/.claude/skills.local.yaml.example

@@ -3,7 +3,8 @@
 # Skills read skills.local.yaml first, falling back to this example.
 
 # Path to the Culture server's agent manifest (suffix → directory mapping).
-# Used by skills that resolve a registered agent suffix to its repo dir.
+# Used by skills that resolve a registered agent suffix to its repo dir —
+# e.g. the agent-config skill / `guild show <suffix>` (suffix mode).
 culture_server_yaml: ~/.culture/server.yaml
 
 # Sibling project paths checked by cross-repo skills (cicd alignment delta,