branch-context-agent

Analyzes git branch changes against active TODO items to detect drift before merging.

Updated Jun 17, 2026

Search Tags:#git #code review #drift detection #merge #github copilot #branch analysis #todo alignment

Ready to run

npx skills add https://github.com/ndestates/ndestates-website --skill branch-context-agent-ndestates

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: branch-context-agent
Source: https://github.com/ndestates/ndestates-website/tree/main/.copilot/skills/branch-context-agent
Command: npx skills add https://github.com/ndestates/ndestates-website --skill branch-context-agent-ndestates

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working on long-lived branches, developers often lose track of whether their changes still align with the original task scope. This Skill summarizes a branch's purpose, compares its changes against the active TODO list, and flags drift before a merge or major work session. ## Core Features & Use Cases - Branch Summarization: Gathers current branch name, commit log, and working tree status to produce a concise context summary. - TODO Alignment Check: Cross-references branch changes against the project's active TODO items and reports an alignment verdict (aligned, partial, or misaligned). - Drift Detection: Identifies risks and out-of-scope changes before merge, with recommended next actions. - Use Case: Before merging a feature branch in ndestates-io, run this Skill to confirm the commits match the planned TODO scope and receive a list of risks and handoff details for the main agent. ## Quick Start Ask the agent to run /branch-context-agent with your branch name to get an alignment verdict and drift report.

Frequently Asked Questions about branch-context-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check if my git branch matches the planned tasks?▼

Run the branch-context-agent with your branch name. It gathers the current branch, commit log, and status, then cross-references changes against the active TODO list and returns an aligned, partial, or misaligned verdict.

How to detect scope drift before merging a feature branch?▼

Invoke this Skill before merging. It compares branch changes to the TODO scope, flags out-of-scope modifications, and reports risks plus recommended next actions so you can correct drift early.

What information does the branch context report include?▼

The report includes the branch purpose summary, changes versus the active TODO, an alignment verdict, identified risks, next actions, and citations of the project caches used during analysis.

Can this Skill be invoked by an orchestrator agent?▼

Yes. The Skill is user-invocable via /branch-context-agent and can also be called by an orchestrator needing branch context. It returns handoff details with branch_context data for the main agent.

What are the limitations of automated branch alignment checks?▼

The analysis depends on the accuracy of the TODO list and project caches. If TODOs are outdated or the cache is stale, the alignment verdict may not reflect the true state of the work.