prepare-branch-context

Analyze the current branch's diff from main and related PR to build context for followup requests. Triggers on "prepare context", "branch context", "catch me up", "what's on this branch".

Jump to install

Repository: trycompai/crm
Last source activity: August 6, 2026 at 07:09
Detected SKILL.md language: English
Stars: 9,916
Forks: 1,300

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

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.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/trycompai/crm --skill prepare-branch-context

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

Prepare Branch Context

Build a comprehensive understanding of the current branch so you can handle followup requests with full context.

Steps

Identify the current branch and base branch:

git branch --show-current
git merge-base HEAD main

Gather the diff from main:

git diff main...HEAD --stat
git diff main...HEAD

Read through the full diff carefully. Understand what files were changed, added, or removed, and what the changes do.

Review the commit history on this branch:

git log main..HEAD --oneline

Read commit messages to understand the progression of changes.

Check for a related PR:

gh pr list --head "$(git branch --show-current)" --json number,title,body,url,state,comments --jq '.[0]'

If a PR exists, read its title, description, and comments for additional context (acceptance criteria, discussion, review feedback).

Summarize your understanding to the user:

What this branch does (high-level purpose)
Key files and areas of the codebase affected
Notable decisions or patterns visible in the changes
Any open review comments or discussion from the PR
Current state (clean, uncommitted changes, etc.)

Signal readiness: Tell the user you're ready for followup questions or tasks related to this branch.

Rules

Do NOT make any changes to files. This skill is read-only.

Read the actual diff content, not just the stat summary. You need to understand the code changes.

If there's no PR, that's fine — just skip that step and note it.

If the diff is very large, focus on understanding the overall structure first, then read key files in detail.

Keep the summary concise but thorough enough that you could confidently make changes to this branch.

If the branch is main or has no divergence from main, tell the user there's nothing to analyze.