agentleFS
ivklgnivklgn/ai-kit/skills/load-branch-changes/SKILL.md

load-branch-changes

Skill12 starsChanged 2 months agoMITView on GitHub

Load current git branch changes (diff, commits, changed files) into session context. Use when the user invokes /load-branch-changes to review, understand, or focus on the current branch's changes compared to the base branch.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run all three commands using the detected $BASE:

    line 23
  2. Distinctive:

    If no changes found, report that the branch has no changes relative to the base branch and stop.

    line 48

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Load Branch Changes

Load the current branch's changes into context and set them as the working focus for the session.

Step 1: Detect Base Branch

BASE=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@')
if [ -z "$BASE" ]; then
  BASE=$(git rev-parse --verify main 2>/dev/null && echo main || echo master)
fi
echo "$BASE"

Step 2: Collect Branch Information

Run all three commands using the detected $BASE:

Changed files:

git diff --name-only $BASE...HEAD

Commit history:

git log $BASE..HEAD --pretty=format:"%h %s"

Full diff with stats:

git diff $BASE...HEAD --patch-with-stat

Step 3: Present Results

Display output in three labeled sections:

  1. Changed Files — file list
  2. Commits — commit log
  3. Diff — full patch with stats

If no changes found, report that the branch has no changes relative to the base branch and stop.

Step 4: Set Session Context

After presenting the results, treat these branch changes as the primary working context for the rest of the session. When the user references "the changes", "the diff", "these files", or similar — they mean the branch changes loaded here. Prioritize changed files and diff when answering questions, suggesting reviews, or proposing edits.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.