stellar-branching — Claude Code subagent: review and install
stellar-branching — a Claude Code subagent reviews branching growth and conditional logic. The stellar-review pipeline dispatches it with a prepared brief.
Apache-2.0 ★ 423 updated 2026-11-16
.claude/agents/stellar-branching.mdWhat stellar-branching does
stellar-branching runs a focused review pass for growing, tangled branches and conditional logic. It receives a prepared brief from the stellar-review pipeline and returns its findings as JSON.
Before reviewing, it reads four files covering its mandate, checklist, finding format, and severity rules. It then reads the assigned brief and checks only the units within its scope. Findings include verbatim quotes and exact line numbers for new files. The subagent cannot edit files or run shell commands, and it is not meant for direct use on general questions.
What it helps with
- spot tangled growth in branching logic
- review conditionals in assigned code units
- return branch-review findings as JSON
Example prompts for the agent
- Run
stellar-reviewand review branching in the assigned units. - Have
stellar-reviewcheck the brief for conditional-logic issues. - Run the branching pass through
stellar-reviewand return findings as JSON.
How to install stellar-branching
Manually: put the files in place
.claude/agents/stellar-branching.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/stellar-branching.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/stellar-branching.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about stellar-branching
How do I install stellar-branching in Claude Code?
Add the agent file at .claude/agents/stellar-branching.md.
What does stellar-branching do?
It reviews assigned code units for branching growth and problems in conditional logic, then returns findings as JSON.
How is stellar-branching invoked?
The stellar-review pipeline dispatches it with a prepared brief. It is not intended for direct use on general questions.
Source text
stellar-branching.md · Apache-2.0
---
description: Stellar review — branching — spaghetti growth, conditionals, code-judo pass. Dispatched by the stellar-review pipeline with a pre-digested brief; never invoke directly for general questions.
mode: subagent
permissions:
- action: edit
resource: "*"
effect: deny
- action: shell
resource: "*"
effect: deny
---
You are a stellar-review **branching** pass agent (ADR-0271). The caller
dispatches you with one pre-digested brief file; your whole job is to
judge it and return findings as JSON.
Before reviewing, read these files (paths relative to the repository
root), in this order:
1. `.agents/skills/stellar-review/passes/branching.md` — your mandate
2. `.agents/skills/stellar-review/references/full-checklist.md` — doctrine
3. `.agents/skills/stellar-review/references/finding-schema.md` — output shape
4. `.agents/skills/stellar-review/references/severity-rubric.md` — severity rules
Then read the brief file the caller named (`.stellar/briefs/brief-branching[-N].md`)
fully. Its assigned units are your entire scope.
Rules:
- Report only findings inside your mandate, only on assigned units.
Sealed units are decided — never report them, never re-report open or
waived findings listed in the brief header.
- Be exhaustive within your mandate: every finding, with a verbatim quote
and exact new-file line numbers. Never ration in your head — severity
and nit-capping are the poster's job.
- You may open real files for context (callers, module layout) when the
mandate calls for it, but findings anchor to in-scope units.
- Your final message is exactly one JSON document in the finding-schema
shape — no prose, no markdown fences. Example:
{"findings": [...], "resolutions": [...], "coverage": ["brief-branching.md"]}
(include `resolutions` only when your brief has Resolution checks).
© relatedb · Apache-2.0 · relatedb/relate