菜单
Keep the agent-facing manual under docs/ in sync with the implementation. Diff-driven from a committed commit baseline; makes conservative, minimal edits only where the code has actually changed user-facing behavior. Run on demand or as part of release prep.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use the Prowl CLI (`prowl`) to inspect or control a running Prowl GUI app and the agent sessions it hosts. Prowl runs several coding agents in parallel, each in its own pane/tab/worktree, so reach for this whenever the user wants to act on a pane other than the current one — check on, coordinate, read from, focus, send text or keys to, open, or close another pane, tab, worktree, split, window, or sibling/neighboring agent. Covers colloquial framings that never say "prowl": "check what the agent in my other window is doing", "are any of my agents running side by side still working or idle?", "tell the agent in my left split to rerun the tests", "send npm run build to the build tab and grab the output", "open ~/proj in a fresh tab", "close that scratch tab I left open". Not for ordinary editing or building inside the Prowl source repo, and not for how-to questions about Prowl's settings, preferences, or keybindings — only when the task is to actually drive panes in the live Prowl app.
Create and maintain curated docs-ai/ records for substantial features and non-trivial, decision-shaping fixes (numbered entries with 000-plan.md before implementation and 001-action.md after). Do not use for reviews, audits, routine investigations, working notes, or status reports unless onevcat explicitly asks for a docs-ai/ record.
Check upstream (supabitapp/supacode) for new changes since the last reviewed baseline.
Build, sign, notarize, and publish a Prowl release.
Bootstrap-verify Prowl changes by launching a debug app with a dedicated PROWL_CLI_SOCKET and driving it from the current Prowl session. Use after implementing Prowl app, terminal, Active Agents, or CLI changes when Codex should validate behavior end-to-end in a separate Prowl instance, including opening worktrees, creating tabs, running commands or agent sessions, reading panes, and falling back to a single-window screenshot of the debug app when the prowl CLI is insufficient.
基于 SOC 职业分类
| name | sync-docs |
| description | Keep the agent-facing manual under docs/ in sync with the implementation. Diff-driven from a committed commit baseline; makes conservative, minimal edits only where the code has actually changed user-facing behavior. Run on demand or as part of release prep. |
Keep the agent-facing documentation under docs/ accurate as the implementation
evolves. This skill is diff-driven (it only looks at source that changed since
a committed baseline) and deliberately conservative (it makes the smallest
edits needed to restore accuracy — it does not rewrite, restyle, or expand the
docs).
Read docs/README.md first for the doc set's structure and intent. The docs are
written for AI agents to read, are plain Markdown, and are designed to be
verifiable: each file lists Keywords/Related, and the reference/ files name
their source-of-truth.
The goal is to keep facts correct with low churn, not to perfect the prose.
Read the baseline. Open docs/.sync-meta.json and read the
last_synced_commit field (the last-synced commit hash).
Diff the implementation since the baseline. List source files that changed:
git diff --name-only <baseline_commit>..HEAD -- \
supacode/ ProwlCLI/ Package.swift Resources/git-wt
If nothing relevant changed, report "Docs up to date as of <HEAD>." then go
to step 6 (bump the baseline) and stop.
Map changed source → docs to re-check. Use this table; only open the docs whose source actually changed. (Most changes touch zero or one doc.)
| Source that changed | Docs to re-check |
|---|---|
supacode/App/AppShortcuts.swift, supacode/Commands/** | reference/keyboard-shortcuts.md (+ shortcut mentions in the relevant components/*.md) |
supacode/Features/Settings/Models/GlobalSettings.swift, RepositorySettings.swift, UserRepositorySettings.swift | reference/settings-fields.md, components/settings.md, components/custom-actions.md |
ProwlCLI/**, supacode/CLIService/** | components/cli.md |
supacode/Clients/CLIInstall/** | components/cli.md, components/settings.md |
supacode/Features/Repositories/**, supacode/Domain/Worktree*.swift, supacode/Domain/Repository*.swift, supacode/Clients/Git/**, Resources/git-wt | components/repositories-and-worktrees.md |
supacode/Features/Terminal/**, supacode/Infrastructure/Ghostty/** | components/terminal.md |
supacode/Features/Canvas/** | components/canvas.md |
supacode/Features/Shelf/** | components/shelf.md |
supacode/Features/CommandPalette/** | components/command-palette.md |
supacode/Features/ActiveAgents/** | components/active-agents.md |
supacode/Domain/AgentDetection/**, supacode/Infrastructure/AgentDetection/** | components/agent-detection.md |
supacode/Clients/Notifications/**, WorktreeTerminalState+Notifications.swift, supacode/Clients/Dock/** | components/notifications.md |
supacode/Features/DiffView/** | components/diff-view.md |
supacode/Clients/Github/** | components/github-pull-requests.md |
supacode/Clients/Updates/**, supacode/Features/Updates/** | components/updates.md |
view-mode switching (supacode/Features/App/**, ContentView.swift) | components/view-modes.md |
overview.md, concepts.md, and README.md only need touch-ups for the
addition/removal of a major feature — leave them alone otherwise.
Verify against the source of truth. For each doc identified, check its falsifiable claims against the authoritative source — not against the diff summary — and apply minimal edits per the conservative rules above:
| Claim type | Source of truth |
|---|---|
| Keyboard shortcuts (key + modifiers + command ID, remappability) | supacode/App/AppShortcuts.swift; menu wiring in supacode/Commands/*.swift |
| Settings field names / types / defaults | supacode/Features/Settings/Models/GlobalSettings.swift, RepositorySettings.swift |
| CLI commands / flags / ranges / error codes / JSON fields | ProwlCLI/** and supacode/CLIService/** (and, if the CLI is installed, prowl <cmd> --help for confirmation) |
| Feature behavior / entry points | the corresponding supacode/Features/** or supacode/Clients/** |
When in doubt whether something is a real, user-facing change, leave the doc as-is and flag it in the report rather than editing.
Check internal links if files moved. If you renamed/added/removed any doc
file, re-run a quick relative-link check so nothing in docs/ is broken.
Bump the baseline. Set last_synced_commit (and last_synced_date, note)
in docs/.sync-meta.json to the current HEAD. This file is committed to
git so the baseline persists across sessions and machines — never leave it
uncommitted.
Report. Output a short summary:
## Docs Sync
Baseline: <old_hash> → <new_hash>
Source files changed in range: <count>
### Updated
- docs/<file> — <one-line what & why>
### Checked, left unchanged (tolerated)
- <area> — <why it didn't need a doc change>
### Needs human decision (not applied)
- <large/ambiguous change> — <what & suggested doc action>
docs/** (which includes
docs/.sync-meta.json); never git add .. If anything in docs/ changed and
you're not on main, open a PR targeting onevcat/Prowl.release skill, on main): commit the doc +
docs/.sync-meta.json changes as their own commit before the version bump and
tag — e.g. git commit -m "Sync docs for <VERSION>". Do not leave them
staged/uncommitted: release.sh aborts on a dirty working tree, and the doc
commit must already be on main so it becomes an ancestor of the tag and ships
inside the release. Bump/tag happen after, never before.docs/.sync-meta.json even when no doc edits were
needed, so the next run starts from a tight diff range. The baseline records the
commit the docs were verified against (the current HEAD at run time) — for a
release that is the code being shipped, captured before the later doc/bump/tag
commits, which is correct (those commits touch no implementation files).