Menu
Show changes compared to base branch (defaults to main). Use when the user asks what changed, wants a summary of branch differences, or says "catch me up".
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Best practices for working with Go codebases. Use when writing, debugging, or exploring Go code, including reading dependency sources and documentation.
Autonomous orchestration loop for hive hc tasks. The high-capability manager model reads pending tasks, delegates implementation to cheaper worker sub-agents, critically reviews their output, and commits only code that passes quality checks. Runs to completion without stopping to ask questions.
Post-implementation design re-evaluation. After a feature reaches a working state through iteration, step back and re-examine what actually got built: are the data structures and algorithms the right fit for the access patterns that emerged, can code paths that grew through iteration be consolidated, and what iteration residue (tests for abandoned designs, dead flags/scaffolding, debug logging) should be deleted. Produces a tiered proposal report and applies only approved changes. Use when the user says "rethink this", "step back and re-evaluate", "is this the right design/data structure", "apply CS fundamentals", or wants a design pass on a working feature branch before PR. Not for bug-hunting (/review) or expression-level polish (/simplify) — this questions the design those skills preserve.
Orchestrate parallel claude and codex CLI agents through tmux to deliver a feature end-to-end. The orchestrator delegates planning, work, and review to spawned agents in tmux windows; it does NOT write or edit code itself. User-invoked only.
Open the current branch's diff (or a specific PR) in Plannotator's browser-based code review UI and act on the returned feedback. Use when the user says "review my changes in plannotator", "open the diff for review", "review this PR in plannotator", "let me annotate the diff", or returns to a session to gate code the agent produced.
Single-pass code review of the current branch (or a diff) that routes the changes to relevant concerns, dispatches fresh-context reviewer sub-agents, verifies findings to strip false positives, and reports a ranked, evidence-backed review. Use when the user asks to review local changes, a branch, or a PR before it goes to humans.
| name | catchup |
| description | Show changes compared to base branch (defaults to main). Use when the user asks what changed, wants a summary of branch differences, or says "catch me up". |
| allowed-tools | Bash(git diff:*),Bash(git log:*),Bash(git status:*),Bash(git branch:*),Read,Grep,Glob |
| argument-hint | [base-branch or additional context] |
| disable-model-invocation | true |
Review what has changed compared to a base branch and provide a comprehensive summary.
User may provide: $ARGUMENTS
These could include:
develop, master, production) — defaults to main if not specified--stat, --name-only)src/components/)git status to understand the current statemain)git diff <base-branch>...HEAD to show changesgit log <base-branch>..HEAD for commits