Skip to main content
subagent CX Codex

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

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/agents/stellar-branching.md
Open on GitHub

What 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-review and review branching in the assigned units.
  • Have stellar-review check the brief for conditional-logic issues.
  • Run the branching pass through stellar-review and return findings as JSON.

How to install stellar-branching

Manually: put the files in place

.claude/agents/stellar-branching.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

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

Similar subagents

All subagents for Code review and refactoring →
branching-strategy-wasp-drone Legion Code Inc. branching-strategy-wasp-drone — a subagent that guides your team through selecting a Git branching model (trunk-based development, GitHub Flow, GitFlow) and resolving merge pain, release workflows, and feature-flag trade-offs. CX Codex ★ 96repo stars git-workflow Galaxy-Dawn git-workflow enforces Git standards: Conventional Commits, branch naming, no-ff merge flows, and conflict resolution. Useful for teams needing consistent version control habits. CX Codex +1 382installs mirrord-db-branching MetalBear mirrord-db-branching is a Claude Code skill that generates and validates mirrord.json database branch configs for isolated schema-change and query testing. CX Codex +1 ★ 31repo stars branching-strategy-stinger Legion Code Inc. branching-strategy-stinger selects a Git branching workflow, handles hotfix routines, and resolves merge versus rebase questions based on your delivery cycle. CX Codex +1 ★ 96repo stars git-flow-manager davila7 git-flow-manager — a Claude subagent that creates Git Flow branches, merges them, tags releases and opens pull requests. Useful when the branching scheme is strict but nobody follows it by hand. CX Codex 3,127installs upgrade-stellar-contracts OpenZeppelin upgrade-stellar-contracts — a skill for upgrading Stellar/Soroban smart contracts with OpenZeppelin's upgradeable module. Use it to make contracts updatable, migrate storage data, or ensure compatibility across bytecode replacements. CX Codex +1 281installs

From the same set18

The whole set →
relate This Claude Code skill guides Python work with Relate, an embedded openCypher graph database. It activates for building a local database, running Cypher queries, and handling query results. CX Codex +1 ★ 423repo stars relate This Claude Code skill guides JavaScript and TypeScript work with Relate, a local graph database queried with openCypher. It covers connections, transactions, and result handling. CX Codex +1 ★ 423repo stars rust-reviewer The rust-reviewer skill for Claude Code and Codex reviews Rust code for ownership, lifetimes, and error handling issues. It examines the whole project, including unsafe blocks and idiomatic Rust patterns. CX Codex +1 ★ 423repo stars agent-backlog-autopilot The agent-backlog-autopilot Claude Code skill takes one agent-backlog task from selection through a pull request. It pauses after the draft checks pass and waits for a human to mark the PR ready for review. CX Codex +1 ★ 423repo stars stellar-code-quality-review The stellar-code-quality-review Claude Code skill audits maintainability, abstraction quality, and file growth. Its staged review examines changes and related code units. CX Codex +1 ★ 423repo stars stellar-structure stellar-structure — a subagent for Claude Code that runs a code structure pass covering size, decomposition, and layer placement. Triggered by the stellar-review pipeline. CX Codex +1 ★ 423repo stars stellar-boundaries Claude Code subagent stellar-boundaries reviews boundaries, abstractions, and type contracts during a code review pipeline. CX Codex +1 ★ 423repo stars stellar-comparison stellar-comparison — a Claude Code subagent for comparison checks in the stellar-review pipeline. It receives a prepared brief and returns findings as JSON. CX Codex +1 ★ 423repo stars

Project sponsors

Companies that keep this analytics open