Agent skill

Explain Changes

by freekmurze in freekmurze/dotfiles

Explain how the code on the current branch works, as an HTML page opened in the browser, written so someone can understand the change and review it.

No licenceAuto-check passedFrontend & Design

Install Explain Changes

skills CLI
$ npx skills add freekmurze/dotfiles --skill explain-changes -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install freekmurze/dotfiles explain-changes --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/freekmurze/dotfiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/config/claude/skills/explain-changes .claude/skills/explain-changes && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
explain-changes
GitHub stars
1k
Token cost
~1.8k tokens
SKILL.md length
1,025 words
Files
2 (incl. references)
Skills in repo
51
Repo updated
First seen
Licence
None found

At a glance

Explain how the code on the current branch works, as an HTML page opened in the browser, written so someone can understand the change and review it.

  • Asked to explain a branch
  • SKILL.md covers Scope, Read beyond the diff, How to write it and Link to the code, plus 1 more section
  • Calls git and gh; reaches github.com
  • Explain these changes

What it does

Explain Changes is an agent skill from freekmurze/dotfiles. Explain how the code on the current branch works, as an HTML page opened in the browser, written so someone can understand the change and review it. Use when asked to explain a branch, explain these changes, walk me through this code, help me review this, or explain what an agent just did. Most useful when someone other than the reader wrote the code and it has to be understood before merging.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files.

It sits in Frontend & Design, covering HTML artifacts.

When your agent uses it

  • Asked to explain a branch
  • Explain these changes
  • Walk me through this code
  • Help me review this

Example prompts

  • “/explain-changes”

What it can do on your machine

Read from SKILL.md and the folder at commit 296be1a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Explain Changes loads about 1.8k tokens when it runs, and up to ~3.8k if it reads all its reference files. Until then it costs about 103 tokens; SKILL.md has 1,025 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~103
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Without a licence we can't republish the file, so here is its outline and opening line. It has 1,025 words (~1,803 tokens).

“Produce a detailed written explanation of everything on this branch, as an HTML page, and open it.”

— opening of SKILL.md by freekmurze
name
explain-changes

Read the full SKILL.md on GitHub

Files

SKILL.md and 1 other file (references) in config/claude/skills/explain-changes of freekmurze/dotfiles.

  • SKILL.md
  • references/page-template.html

Open the folder on GitHubat commit 296be1a

Compare with similar skills

Explain Changes next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Explain Changes compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Explain Changes this skillfreekmurze/dotfiles1k—~1.8kAutomated safety check: PassNone
LobeHub Interactive Prototypelobehub/lobehub83k—~1.6kAutomated safety check: PassCustom licence
Paperclip Pagepaperclipai/paperclip99k—~1kAutomated safety check: PassMIT
Openkb Deck NeonVectifyAI/OpenKB4.7k1 repos~4.3kAutomated safety check: PassApache-2.0
Webhome Homepage Builderwebhtv/webhtv1.7k—~3.8kAutomated safety check: PassGPL-3.0
Solo Artifactssolo-agent/solo697—~961Automated safety check: PassMIT

Similar skills

  • Builds single-file interactive HTML prototypes rendered with the real LobeHub UI components and written as production-style React, so they can later be split into files.

    83k GitHub stars~1.6k tokensUpdated today
    Frontend & DesignAuto-check passed
  • Paperclip Page

    paperclipai/paperclip

    Publish static HTML pages and asset folders to the Paperclip S3/CloudFront page host.

    99k GitHub stars~1k tokensUpdated today
    Frontend & DesignAuto-check passed
  • Openkb Deck Neon

    VectifyAI/OpenKB

    A skill your agent uses when the user asks the openkb chat to make a deck / slide presentation / PPT / slides / 演示稿 / 幻灯片 from their compiled KB content AND wants a dark, high-tech, neon / glow /…

    4.7k GitHub starsUsed in 1 repo~4.3k tokens
    Frontend & DesignAuto-check passed
  • Build, review, debug, reverse-engineer data sources for, and package FongMi/WebHome custom homepage single-file HTML.

    1.7k GitHub stars~3.8k tokensUpdated today
    Frontend & DesignAuto-check passed
  • Solo Artifacts

    solo-agent/solo

    A skill your agent uses when a Solo task or thread should become an interactive, reviewable, self-contained HTML artifact for progress/status, review/decision, or comparison/leaderboard work inside…

    697 GitHub stars~961 tokensUpdated 25 days ago
    Frontend & DesignAuto-check passed
  • Paper2html

    QuZhan51496/paper2anything

    Convert an academic paper PDF into a publish-ready, self-contained single-page project homepage (a self-contained index.html) — the kind of paper landing page researchers host on GitHub Pages.

    468 GitHub stars~3.3k tokensUpdated 2 mo ago
    Frontend & DesignAuto-check: notes

More from freekmurze/dotfiles

All 51 skills in this repo
  • Social Content

    freekmurze/dotfiles

    When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms.

    1k GitHub starsUsed in 23 repos~2.1k tokens
    Auto-check passed
  • Email Sequence

    freekmurze/dotfiles

    When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program.

    1k GitHub starsUsed in 19 repos~2k tokens
    Auto-check passed
  • Referral Program

    freekmurze/dotfiles

    When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy.

    1k GitHub starsUsed in 17 repos~1.8k tokens
    Auto-check passed
  • Typefully

    freekmurze/dotfiles

    Create, schedule, and manage social media posts via Typefully.

    1k GitHub starsUsed in 2 repos~3.4k tokens
    Auto-check: notes
  • Onboarding Cro

    freekmurze/dotfiles

    When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value.

    1k GitHub starsUsed in 16 repos~1.6k tokens
    Auto-check passed
  • Ab Test Setup

    freekmurze/dotfiles

    When the user wants to plan, design, or implement an A/B test or experiment.

    1k GitHub starsUsed in 15 repos~1.8k tokens
    Auto-check passed

Questions about Explain Changes

What does Explain Changes do?

Explain how the code on the current branch works, as an HTML page opened in the browser, written so someone can understand the change and review it. Explain Changes is an agent skill from freekmurze/dotfiles. Explain how the code on the current branch works, as an HTML page opened in the browser, written so someone can understand the change and review it.

When should I use Explain Changes?

Explain Changes fits situations like: asked to explain a branch; explain these changes; walk me through this code; help me review this.

How do I install Explain Changes in Claude Code?

Run `npx skills add freekmurze/dotfiles --skill explain-changes -a claude-code`. Or copy the skill folder (config/claude/skills/explain-changes in freekmurze/dotfiles) into .claude/skills/explain-changes in your project. Claude Code loads it when a task matches its description.

How do I install Explain Changes in Codex?

Run `npx skills add freekmurze/dotfiles --skill explain-changes -a codex`. Or copy the skill folder (config/claude/skills/explain-changes in freekmurze/dotfiles) into .agents/skills/explain-changes in your project. Codex loads it when a task matches its description.

Can I use Explain Changes in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add freekmurze/dotfiles --skill explain-changes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/explain-changes, .gemini/skills/explain-changes, .github/skills/explain-changes and .opencode/skills/explain-changes in your project.

What does Explain Changes need to run?

Going by SKILL.md and its folder, Explain Changes needs the command-line tools its instructions call (git and gh).

Does Explain Changes access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Explain Changes safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Explain Changes use?

No licence was found for Explain Changes or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Explain Changes use?

About 1.8k tokens (SKILL.md is roughly 7.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2k tokens, read only when the agent opens those files.

What are the alternatives to Explain Changes?

Skills that share tags, products or a category with Explain Changes: LobeHub Interactive Prototype (lobehub/lobehub, 83k stars), Paperclip Page (paperclipai/paperclip, 99k stars), Openkb Deck Neon (VectifyAI/OpenKB, 4.7k stars) and Webhome Homepage Builder (webhtv/webhtv, 1.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Explain Changes?

freekmurze (a GitHub user) maintains it in freekmurze/dotfiles, which has 1,012 GitHub stars. The repository holds 51 skills in this directory. The repository was last updated on October 5, 2026.

Source: freekmurze/dotfiles on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.