Menu
(no description)
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
Review changes since a fixed point along two axes โ Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match the originating shape, revision description, issue, or PRD?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, revision, PR, working-copy changes, or asks to "review since X".
Control Herdr, a terminal multiplexer for coding agents. Use only when the user explicitly mentions Herdr or asks to use Herdr to inspect or control panes, tabs, workspaces, terminals, commands, or communication with another agent. Do not use merely because a task could benefit from a background terminal, delegation, or parallel work.
Use when the user asks for a rich explanation of a code change, diff, branch, or PR. Produces an interactive HTML page, a Notion page, or an interactive Obsidian vault note.
Session mode โ coordinate only, delegate all actual work to background minion subagents
Interview-style session that aligns a plan with the existing domain vocabulary, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Transform a workflow description into affordance tables showing UI and Code affordances with their wiring. Use to map existing systems or design new ones from shaped parts.
| name | gathering-context |
| description | (no description) |
| disable-model-invocation | true |
When I tell you to gather context about something, follow these 8 steps exactly. Start by reading them all aloud, then commit to following them in order. Say the name of each step as you do it. 1. tree base_dir โ Run tree (or similar) on the top-level project dir to scan for docs or overviews. 2. tree subdir_of_interest โ Do a full-depth listing of the relevant subdirectory. Donโt worry about size yet. 3. note likely files โ Skim filenames. Donโt open them. Just write down likely candidates based on naming. 4. rg signatures โ Use ripgrep to extract structural keywords (language-specific, e.g. def, class, func, interface, etc.). Example:
rg -n '(def|class|function|interface|type|struct|module|macro|const|static|trait)' some_file
5. read signatures โ Pick the symbols/types/functions that seem relevant and read them in full.
6. expand context โ Read surrounding code, comments, and sibling functions/types for broader understanding.
7. loop with knowledge โ With new insight, re-start at step 1 looking for new possibly relevant files.
8. repeat until full โ Loop until youโre confident the important context has been found.