inspect-profilelisted

# inspect-profile Read-only. Wraps `bin/inspect-profile.sh`. Loads a profile via `load-profile.sh` (user profiles shadow starters with the same name) and renders a human-readable summary. ## 1. Resolve the profile name - The user names it explicitly most of the time ("what does `nextjs-prototype` do"). Use that. - If the user is ambiguous ("what does my profile do"), ask — the skill doesn't infer from the repo. For "show this repo's setup", route to `explain-state` instead. - Names match the regex `^[a-z0-9][a-z0-9-]*$`. Reject anything else with a clear message rather than handing a bad name to the backend. ## 2. Invoke ``` bin/inspect-profile.sh <name> [--user-root <dir>] ``` `--user-root` defaults to `~/.claude/nyann`. Only override when the user says something like "check my team-installed profile at `<path>`". ## 3. Read the output back The backend already formats sections (Profile, Stack, Branching, Hooks, Extras, Conventions, Documentation, GitHub integration). Your job is to relay those faithfully and add context when the user asks a follow-up. Don't re-summarize — the backend's blurbs for each hook (e.g. "ESLint runs on staged JS/TS") are authoritative. When the user asks "is this the right profile for my repo", do NOT guess — suggest running `explain-state` (reads the repo) and comparing, or running `doctor` (reports drift against a chosen profile). ## 4. Handle "not found" Exit code 2 means the profile isn't in user root or starters. The backend