New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Git History Analyzer

by udecode in udecode/plate

Performs archaeological analysis of git history to trace code evolution, identify contributors, and understand why code patterns exist.

Custom licenceAuto-check passedDevelopment

Install Git History Analyzer

skills CLI
$ npx skills add udecode/plate --skill git-history-analyzer -a claude-code

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

GitHub CLI
$ gh skill install udecode/plate git-history-analyzer --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/udecode/plate.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/git-history-analyzer .claude/skills/git-history-analyzer && 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
git-history-analyzer
GitHub stars
17k
Token cost
~1.1k tokens
SKILL.md length
525 words
Files
1
Skills in repo
78
Repo updated
First seen
Licence
Custom licence

At a glance

Performs archaeological analysis of git history to trace code evolution, identify contributors, and understand why code patterns exist.

  • Works in 5 steps: File Evolution Analysis: Run git log… → Code Origin Tracing: Run git blame -w -C… → Pattern Recognition: Run git log --grep=… → …
  • You need historical context for code changes
  • Calls git
  • Tasks that involve Git workflow

What it does

Git History Analyzer is an agent skill from udecode/plate. Performs archaeological analysis of git history to trace code evolution, identify contributors, and understand why code patterns exist. Use when you need historical context for code changes.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Git workflow. It works with Git. The repository describes itself as: Rich-text editor with AI and shadcn/ui.

When your agent uses it

  • You need historical context for code changes
  • Tasks that involve Git workflow

Example prompts

  • “Use the git-history-analyzer skill to perform archaeological analysis of git history to trace code evolution, identify contributors, and understand…”
  • “/git-history-analyzer”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. File Evolution Analysis: Run git log --follow --oneline -20 to trace recent history. Identify major refactorings, renames, and significant…
  2. Code Origin Tracing: Run git blame -w -C -C -C to trace the origins of specific code sections, ignoring whitespace changes and following…
  3. Pattern Recognition: Run git log --grep= --oneline to identify recurring themes, issue patterns, and development practices.
  4. Contributor Mapping: Run git shortlog -sn -- to identify key contributors and their relative involvement.
  5. Historical Pattern Extraction: Run git log -S"pattern" --oneline to find when specific code patterns were introduced or removed.

What it can do on your machine

Read from SKILL.md and the folder at commit a860762. 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

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

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    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

Git History Analyzer loads about 1.1k tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 525 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~53
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

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

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 525 words (~1,053 tokens).

“Context: The user wants to understand the history and evolution of recently modified files. user: "I've just refactored the authentication module. Can you analyze the historical context?" assistant: "I'll use the git-history-analyzer agent to examine the evolution of the authentication…”

— opening of SKILL.md by udecode, Custom licence
name
git-history-analyzer
model
inherit

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .agents/skills/git-history-analyzer of udecode/plate.

Open the folder on GitHubat commit a860762

Compare with similar skills

Git History Analyzer 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.

Git History Analyzer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Git History Analyzer this skilludecode/plate17k—~1.1kAutomated safety check: PassCustom licence
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Code Design Rationale Investigatorcursor/plugins10k9 repos~2.6kAutomated safety check: PassNone
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Migrate Internal Package into GhostTryGhost/Ghost55k—~3.8kAutomated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Code Design Rationale Investigator

    cursor/plugins

    Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    10k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Migrate Internal Package into Ghost

    TryGhost/Ghost

    Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.

    55k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Git Merge Conflict Resolver

    tailcallhq/forgecode

    Resolves Git merge conflicts with a plan-first workflow that keeps both sides' intent, regenerates lock files and backs up deleted-but-modified files.

    7.6k GitHub starsUsed in 1 repo~4.5k tokens
    DevelopmentAuto-check passed

More from udecode/plate

All 78 skills in this repo

  • React Useeffect

    udecode/plate

    React useEffect best practices from official docs. An agent skill from udecode/plate.

    17k GitHub starsUsed in 6 repos~573 tokens
    Auto-check passed

  • Video Transcripts

    udecode/plate

    Generate structured video transcripts from local files or video URLs using Gemini Files API.

    17k GitHub stars~1.5k tokensUpdated today
    Auto-check passed

  • Plate Plugin Creator

    udecode/plate

    Build new Plate plugins with Slate-first architecture, sane typing, and explicit React/Plate wrapper boundaries.

    17k GitHub stars~2.3k tokensUpdated today
    Auto-check passed

  • Plate UI

    udecode/plate

    Build new shadcn-style components for Plate's registry and editor surfaces.

    17k GitHub stars~2.6k tokensUpdated today
    Auto-check passed

  • Best Practices Researcher

    udecode/plate

    Researches and synthesizes external best practices, documentation, and examples for any technology or framework.

    17k GitHub stars~2k tokensUpdated today
    Auto-check passed

  • Frontend Design

    udecode/plate

    Build web interfaces with genuine design quality, not AI slop.

    17k GitHub stars~3.6k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Git History Analyzer

What does Git History Analyzer do?

Performs archaeological analysis of git history to trace code evolution, identify contributors, and understand why code patterns exist. Git History Analyzer is an agent skill from udecode/plate. Performs archaeological analysis of git history to trace code evolution, identify contributors, and understand why code patterns exist.

When should I use Git History Analyzer?

Git History Analyzer fits situations like: you need historical context for code changes; tasks that involve Git workflow.

How do I install Git History Analyzer in Claude Code?

Run `npx skills add udecode/plate --skill git-history-analyzer -a claude-code`. Or copy the skill folder (.agents/skills/git-history-analyzer in udecode/plate) into .claude/skills/git-history-analyzer in your project. Claude Code loads it when a task matches its description.

How do I install Git History Analyzer in Codex?

Run `npx skills add udecode/plate --skill git-history-analyzer -a codex`. Or copy the skill folder (.agents/skills/git-history-analyzer in udecode/plate) into .agents/skills/git-history-analyzer in your project. Codex loads it when a task matches its description.

Can I use Git History Analyzer 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 udecode/plate --skill git-history-analyzer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/git-history-analyzer, .gemini/skills/git-history-analyzer, .github/skills/git-history-analyzer and .opencode/skills/git-history-analyzer in your project.

What does Git History Analyzer need to run?

Going by SKILL.md and its folder, Git History Analyzer needs the command-line tools its instructions call (git).

Does Git History Analyzer access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Git History Analyzer 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 Git History Analyzer use?

Git History Analyzer has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Git History Analyzer use?

About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Git History Analyzer?

Skills that share tags, products or a category with Git History Analyzer: Finishing a Development Branch (obra/superpowers, 296k stars), Code Design Rationale Investigator (cursor/plugins, 10k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Migrate Internal Package into Ghost (TryGhost/Ghost, 55k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Git History Analyzer?

udecode (a GitHub organization) maintains it in udecode/plate, which has 16,638 GitHub stars. The repository holds 78 skills in this directory. The repository was last updated on October 7, 2026.

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