Menú
Check upstream (supabitapp/supacode) for new changes since the last reviewed baseline.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
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.
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.
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.
| name | check-upstream-changes |
| description | Check upstream (supabitapp/supacode) for new changes since the last reviewed baseline. |
Check upstream (supabitapp/supacode) for new changes since the last reviewed baseline.
Follow these steps:
Read docs-ai/017-upstream-sync-process/upstream-ledger.md and extract the Upstream Baseline commit hash and date.
Fetch the upstream remote:
git fetch upstream main --quiet
List all commits on upstream/main that are newer than the baseline commit:
git log --oneline <baseline_commit>..upstream/main
If there are no new commits, report "No new upstream changes since <baseline_commit> ()." and stop.
For each new commit (or group of related commits), produce a one-line summary including:
docs-ai/017-upstream-sync-process/upstream-ledger.md Old Log for context)Categorize commits into:
Present the briefing in this format:
## Upstream Changes Briefing
Baseline: <hash> (<date>)
Latest upstream: <hash> (<date>)
New commits: <count>
### Needs Attention
- `<hash>` <summary> — <reason>
### Safe to Merge
- `<hash>` <summary>
### Recommended Next Step
<action suggestion>
Do NOT modify any files or run sync. This command is read-only reconnaissance.