Agent skill

Git Context

Search git history for context — commit messages, blame, related changes, impact analysis

MITAuto-check passedDevelopment

Install Git Context

skills CLI

$ npx skills add jellydn/my-ai-tools --skill git-context -a claude-code

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

GitHub CLI

$ gh skill install jellydn/my-ai-tools git-context --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/jellydn/my-ai-tools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/git-context .claude/skills/git-context && 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/

Paste into Claude Code

Install the "git-context" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/git-context into .claude/skills/git-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-context", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/jellydn/my-ai-tools/tree/main/skills/git-context

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add jellydn/my-ai-tools --skill git-context -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install jellydn/my-ai-tools git-context --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/git-context .agents/skills/git-context && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "git-context" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/git-context into .agents/skills/git-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-context", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add jellydn/my-ai-tools --skill git-context -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install jellydn/my-ai-tools git-context --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/git-context .cursor/skills/git-context && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "git-context" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/git-context into .cursor/skills/git-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-context", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/jellydn/my-ai-tools.git --path skills/git-context

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add jellydn/my-ai-tools --skill git-context -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install jellydn/my-ai-tools git-context --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/git-context .gemini/skills/git-context && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "git-context" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/git-context into .gemini/skills/git-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-context", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install jellydn/my-ai-tools git-context

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add jellydn/my-ai-tools --skill git-context -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/git-context .github/skills/git-context && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "git-context" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/git-context into .github/skills/git-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-context", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add jellydn/my-ai-tools --skill git-context -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install jellydn/my-ai-tools git-context --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/git-context .opencode/skills/git-context && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "git-context" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/git-context into .opencode/skills/git-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-context", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: git-context
GitHub stars: 123
Token cost: ~1.1k tokens
SKILL.md length: 223 words
Files: 1
Skills in repo: 35
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Search git history for context — commit messages, blame, related changes, impact analysis

Tasks that involve Git workflow
SKILL.md covers When to Use, What It Does, How to Execute and Decision Tree, plus 3 more sections
Calls git
Tasks that involve Commit messages

What it does

Git Context is an agent skill from jellydn/my-ai-tools. Search git history for context — commit messages, blame, related changes, impact analysis

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. Compatibility notes: cline, claude, opencode, amp, codex, gemini, cursor, pi

It sits in Development, covering Git workflow and Commit messages. It works with Git. The repository describes itself as: Comprehensive configuration management for AI coding tools - Replicate my complete setup for Claude Code, OpenCode, Amp, Li, Codex and Claude Code Switch with custom… The licence is MIT.

When your agent uses it

Tasks that involve Git workflow
Tasks that involve Commit messages

Example prompts

“/git-context”

Requirements

Compatibility (from SKILL.md): cline, claude, opencode, amp, codex, gemini, cursor, pi

What it can do on your machine

Read from SKILL.md and the folder at commit 163951e. 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.
Compatibility
cline, claude, opencode, amp, codex, gemini, cursor, pi
From compatibility in the SKILL.md frontmatter.

Context cost

Git Context loads about 1.1k tokens when it runs. Until then it costs about 25 tokens; SKILL.md has 223 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~25
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

The full file from jellydn/my-ai-tools at commit 163951e, republished under its MIT licence (© jellydn). 223 words, ~1,058 tokens.

Download SKILL.mdSave it as .claude/skills/git-context/SKILL.md (or your agent's skills folder).

name: git-context
description: Search git history for context — commit messages, blame, related changes, impact analysis
compatibility: cline, claude, opencode, amp, codex, gemini, cursor, pi
license: MIT
hint: Use to understand why code was written a certain way or find related changes
user-invocable: true

Git Context

When to Use

Use this skill when:

Understanding why code was written a certain way
Finding related changes across the codebase
Tracing the evolution of a feature or pattern
Identifying who has expertise in a module
Finding past bug fixes or regressions in an area

What It Does

Searches git history to build context about the codebase, using a combination of native git commands and the sem MCP tool for deeper analysis. Helps answer "why was this done this way?" and "what changed recently in this area?"

How to Execute

Find Recent Changes to a Module

bash

# Recent commits touching this area
git log --oneline --all -20 -- path/to/module/

# Who works on this area most
git shortlog -sn -- path/to/module/

# When a specific function was introduced
git log -S "functionName" --oneline -- path/to/module/

Trace a Function's History

bash

# When was this function introduced?
git log -S "export function calculateTotal" --oneline

# Who has modified it?
git blame path/to/file.ts -L 10,30

# What was the commit message?
git show <commit-hash> --no-patch

bash

# Files changed together in the same commits
git log --all --name-only -- path/to/changed/file.ts | head -20

# Find commits that reference a ticket or pattern
git log --all --grep="fix|bug|hotfix" --oneline -20

Using `sem` for Deeper Analysis

bash

# Entity-level blame (function level)
sem blame path/to/file.ts --function processOrder

# Impact analysis
sem impact path/to/file.ts --function processOrder

# Compare branches at function level
sem diff main..HEAD -- path/to/file.ts

Cross-Session Context

bash

# Search past agent sessions about this module
ctx search "this module" path/to/module/

# Find past discussions about related changes
ctx search "bug fix" path/to/module/

Decision Tree

┌────────────────────────────┬────────────────────────┐
│ Need this                   │ Use this               │
├────────────────────────────┼────────────────────────┤
│ What changed recently      │ git log -20 -- path/   │
│ Who works on this module   │ git shortlog -sn path/ │
│ Why was this line added    │ git blame path/to/file │
│ When was function added    │ git log -S "funcName"  │
│ What else changed together │ git log --name-only    │
│ Impact of changing X       │ sem impact path/func   │
│ Past agent work on this    │ ctx search "topic"     │
└────────────────────────────┴────────────────────────┘

Common Patterns

Pre-Implementation Check

Before implementing a change, check:

bash

# 1. Recent changes to affected modules
git log --oneline --all -10 -- src/feature/

# 2. Who has expertise
git shortlog -sn -- src/feature/ | head -5

# 3. Related commits (ticket/branch references)
git log --all --grep="feature-name" --oneline

# 4. Past bugs in this area
git log --all --grep="bug|fix|error" --oneline -10 -- src/feature/

Post-Change Verification

After implementing, verify:

bash

# 1. What did I change?
git diff --stat

# 2. Are there unrelated changes?
git diff --cached --name-only

# 3. Did I miss anything?
git diff HEAD --name-only  # Unstaged changes

Tips

Commit messages matter: Write clear messages — they become the primary documentation
Use git log -S over grep for history: grep scans the working tree; git log -S scans history
Combine with ctx: Past agent sessions often contain context that git history doesn't
Be specific with paths: git log -- path/ filters to relevant commits, reducing noise
Use --all for complete picture: Default git log only shows current branch history

Integration with Other Skills

Use before /blindspots to gather initial context
Use during context-discovery for deep git history analysis
Log surprising git history findings in implementation-logger

Files

Just SKILL.md in skills/git-context of jellydn/my-ai-tools.

Open the folder on GitHubat commit 163951e

Compare with similar skills

Git Context 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 Context compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Git Context this skilljellydn/my-ai-tools	123	—	~1.1k	Automated safety check: Pass	MIT	today
ToolJet Multi-Repo CommitToolJet/ToolJet	41k	—	~1.3k	Automated safety check: Pass	AGPL-3.0	today
Git Workflow and Versioningaddyosmani/agent-skills	102k	2 repos	~3.5k	Automated safety check: Notes	MIT	4 days ago
React Router Pull Request Creatorremix-run/react-router	57k	—	~2.5k	Automated safety check: Pass	MIT	yesterday
Saleor Commit Workflowsaleor/saleor	23k	—	~575	Automated safety check: Pass	BSD-3-Clause	yesterday
Emoji Commit ConventionsbaptisteArno/typebot.io	11k	—	~424	Automated safety check: Pass	Custom licence	yesterday

Similar skills

ToolJet Multi-Repo Commit
ToolJet/ToolJet
Commits changes across ToolJet's root repo and its server/ee and frontend/ee submodules, writing messages from the diffs and updating submodule pointers in order.
41k GitHub stars~1.3k tokensUpdated today
DevelopmentAuto-check passed
Git Workflow and Versioning
addyosmani/agent-skills
Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.
102k GitHub starsUsed in 2 repos~3.5k tokens
DevelopmentAuto-check: notes
React Router Pull Request Creator
remix-run/react-router
Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.
57k GitHub stars~2.5k tokensUpdated yesterday
DevelopmentAuto-check passed
Saleor Commit Workflow
saleor/saleor
Commits changes in the Saleor codebase and works through pre-commit hook failures from ruff, mypy, the GraphQL schema check and the migrations check.
23k GitHub stars~575 tokensUpdated yesterday
DevelopmentAuto-check passed
Emoji Commit Conventions
baptisteArno/typebot.io
Sets the repository's convention for commit messages and pull request titles: one emoji prefix for the main intent, a concise title and clean follow-up commits.
11k GitHub stars~424 tokensUpdated yesterday
DevelopmentAuto-check passed
Draft Pull Request Creator
wordpress-mobile/WordPress-Android
Commits and pushes current changes, writes a pull request title and body from the branch history and template, and opens a draft PR on GitHub after you approve it.
3.2k GitHub stars~881 tokensUpdated yesterday
DevelopmentAuto-check: notes

Questions about Git Context

What does Git Context do?

Search git history for context — commit messages, blame, related changes, impact analysis. Git Context is an agent skill from jellydn/my-ai-tools.

When should I use Git Context?

Git Context fits situations like: tasks that involve Git workflow; tasks that involve Commit messages.

How do I install Git Context in Claude Code?

Run `npx skills add jellydn/my-ai-tools --skill git-context -a claude-code`. Or copy the skill folder (skills/git-context in jellydn/my-ai-tools) into .claude/skills/git-context in your project. Claude Code loads it when a task matches its description.

How do I install Git Context in Codex?

Run `npx skills add jellydn/my-ai-tools --skill git-context -a codex`. Or copy the skill folder (skills/git-context in jellydn/my-ai-tools) into .agents/skills/git-context in your project. Codex loads it when a task matches its description.

Can I use Git Context 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 jellydn/my-ai-tools --skill git-context -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-context, .gemini/skills/git-context, .github/skills/git-context and .opencode/skills/git-context in your project.

What does Git Context need to run?

Going by SKILL.md and its folder, Git Context needs the command-line tools its instructions call (git). Compatibility (from SKILL.md): cline, claude, opencode, amp, codex, gemini, cursor, pi.

Does Git Context 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 Context 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 Context use?

Git Context is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Git Context 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 Context?

Skills that share tags, products or a category with Git Context: ToolJet Multi-Repo Commit (ToolJet/ToolJet, 41k stars), Git Workflow and Versioning (addyosmani/agent-skills, 102k stars), React Router Pull Request Creator (remix-run/react-router, 57k stars) and Saleor Commit Workflow (saleor/saleor, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Git Context?

jellydn (a GitHub user) maintains it in jellydn/my-ai-tools, which has 123 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 7, 2026.

Source: jellydn/my-ai-tools on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Git Context

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Compatibility

Context cost

Safety

SKILL.md

Git Context

When to Use

What It Does

How to Execute

Find Recent Changes to a Module

Trace a Function's History

Find Related Changes

Using sem for Deeper Analysis

Cross-Session Context

Decision Tree

Common Patterns

Pre-Implementation Check

Post-Change Verification

Tips

Integration with Other Skills

Files

Compare with similar skills

Similar skills

More from jellydn/my-ai-tools

Related

Questions about Git Context

Using `sem` for Deeper Analysis