Branch Review

To audit unmerged git branches and generate a summary, this Skill delegates per-branch analysis to a branch-review agent and writes a CHANGES.md file at the repository root with evidence and recommended actions.

Reviewing branch state without bloating the main context is achieved by delegating heavy per-branch investigation to a subagent, which returns only the final recommendations to the main conversation.

You can automatically generate a CHANGES.md file at the repository root by triggering the branch review process, which classifies unmerged branches and writes their state evidence directly to the file.

Yes, you can automate merge and prune recommendations for unmerged branches by running the branch audit, which classifies each branch and outputs suggested actions in the generated CHANGES.md.

The branch review process requires no external dependencies or components, operating as a thin stub that invokes the built-in Agent tool with the branch-review subagent type.

You should not use an automated branch audit agent if your repository lacks unmerged branches or if you need to manually curate the CHANGES.md file instead of relying on automated per-branch evidence collection.