メニュー
Use when an agent hits friction with anu itself or is asked to capture, triage, or act on an anu rough edge with `anu recurse`. Covers the recurse backlog, the safety rule for live config, and when to auto-fix versus propose only.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Open and drive a REAL Chromium browser pane inside anu's tmux session. Use this whenever you need to actually SEE or interact with a web page — check a localhost dev preview after starting a dev server, verify a deploy looks right, read a docs/page that needs JavaScript, reproduce a UI bug, or fill out / click through a web form. Renders a real page (JS/CSS/Canvas/WebGL) via the kitty graphics protocol, in the same Chromium the human sees, so they watch your actions live. Drive it with the `browser` command or the browser_* MCP tools (open/navigate/screenshot/read/snapshot/eval/click/crop/type).
Generate a repo dossier as one fixed-template black-and-white HTML page in the anu atlas (~/.anu/atlas/<repo>): summary, component tree, dependency graph, choices made, divergences, open questions. Fans out reader agents via the Workflow tool; archives each run for diffing. Invoked by /map. Use when the user runs /map or asks to map, explain, or explore this repo as a dossier.
Understand a repository — a black-and-white, table-first Load-Bearing Ledger that ranks every file by structural importance and explains why. Personalized PageRank over the bash-call + python-import graph (utility-down-weighted, entry-point-seeded) is the rank; each row carries a reason vector (imported-by, churn/hotspot, ownership, entry-point, cycle) so no number is bare. Deterministic, reproducible, no LLM — the same parse→JSON→fixed-template→~/.anu/grok/<repo> pattern as scene/trail/git. Use when the user runs `grok` or asks to understand/see the shape of a repo, what files matter, what's load-bearing, what's linked most, or what to read first.
You back a chat as a persistent working agent. Do the turn's work in your terminal (it's shown live to the person); write only your concise final answer to $ANU_CHAT_REPLY, which they read as your reply.
Produce a live rendered artifact (a chart, a computation, a small notebook) that flows inline into your chat answer — when, and only when, running code or plotting would genuinely serve the answer. You decide; writing the file is the only signal.
Git for agents — the cockpit that composes the commit DAG (scene) with the commitments (trail) into ONE graph joined by commit SHA, rendered as four lenses — Evolution (the commit DAG carrying the why, with counterfactual edges = the road not taken), Research (the commitment/hypothesis map), Commitments (what governs each scope), Live (agents now). One surface, lenses not modes; the commit is the truth, the rest decorates it. Run `gfa` (provisional command) → ~/.anu/git/<repo>/index.html. Use when the user wants to see a project evolving WITH its decisions and roads-not-taken, runs `gfa`, or asks for the git-for-agents view.
| name | anu-recurse |
| description | Use when an agent hits friction with anu itself or is asked to capture, triage, or act on an anu rough edge with `anu recurse`. Covers the recurse backlog, the safety rule for live config, and when to auto-fix versus propose only. |
Use recurse when the tool substrate gets in the way: pane delivery, spawn ergonomics, chat pad behavior, box containment, swarm coordination, hooks, or cross-harness instructions.
Record the rough edge immediately:
anu recurse "pane spawn has no --cwd for project-routed workers"
Good notes include the capability, symptom, likely surface, and a minimal repro.
Optional inline tokens help classification: capability=pane surface=bin severity=low.
anu recurse act <id> follows two tiers:
surface=bin and severity low or med. Act on a branch/worktree,
implement the narrow fix, run the relevant tests/bash/* plus
tests/bash/smoke_test.sh, commit, and open a PR with gpr. Do not merge.surface=config or severity high. Propose only. Leave the item with
status proposed and a concrete fix sketch for a human or reviewer agent.Never hot-patch live config/ to fix anu mid-session. The config tree is loaded by
the running IDE and can break every pane at once. Recurse work is always:
branch/worktree -> test -> PR/gate -> merge
Plugin/bin surfaces are safer than config because they are invoked per command, but on this machine they may still be the live installed tool through the anu repo symlink. Treat all recurse changes as branch-first.
tests/bash/smoke_test.sh.