Git Lore

Captures, queries, and configures decision context in native Git trailers. Use for non-trivial commit messages, constraints, rejected alternatives, directives, test gaps, Lore history queries, or installing Lore rules in project or global agent instructions.

9 stars 1 forksGit & Code Review Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add kargnas/skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add kargnas/skills --skill git-lore
Manual install
git clone --depth 1 https://github.com/kargnas/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/git-lore ~/.claude/skills/git-lore

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Git Lore

Preserve decision context beside code by using Git's native commit trailers. Route commit writing and history queries through one skill.

## Route the Request

| Request | Mode |
|---|---|
| Write or perform a non-trivial commit | Commit mode |
| Find constraints, rejected options, directives, verification gaps, or other Lore data in history | Query mode |
| Configure Lore rules in project or global agent instructions | Setup mode |

Repository instructions remain authoritative. Lore supplements existing commit-message rules; it does not replace Conventional Commits, language rules, or repository-specific formats.

## Commit Mode

1. Inspect the staged diff and the verified work from the current task. If nothing is staged, stop and report it; do not stage files unless the user authorized staging them. Never stage unrelated files.
2. Write the summary and body in the repository's required format.
   If none exists, use a locale-appropriate summary that names the resulting
   change: an imperative phrase in English. (or a concise noun phrase in Korean if the user or other rules explicitly want to write in Korean)
   Add an optional body explaining why; do not assume Conventional Commits.
3. Harvest only decision facts supported by the work. Never invent constraints, rejected options, or tests.
4. Append only useful trailers after a blank line.
5. Re-read the message and remove trailers that merely restate the diff.
Read the full skill on GitHub

Details

Skill name
git-lore
Repository
kargnas/skills
Path
skills/git-lore/SKILL.md
Repo updated
18 November 2026

FAQ

What does the Git Lore skill do?

Captures, queries, and configures decision context in native Git trailers. Use for non-trivial commit messages, constraints, rejected alternatives, directives, test gaps, Lore history queries, or installing Lore rules in project or global agent instructions.

How do I install the Git Lore skill?

Claude Code plugin: /plugin marketplace add kargnas/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Git Lore popular?

It lives in kargnas/skills, which has 9 GitHub stars and 1 forks.

Related skills

AI Ready

9

kargnas/skills

Use only when the user asks to make the repo AI-ready or AI-optimized (AGENTS.md migration, debugging/testing setup, docs). Do not run on your own.

AI, LLMs & Agents

Design Frontend Sangrak

9

kargnas/skills

Use when starting frontend work in a project with no existing design system, when building or theming UI with shadcn/ui or Tailwind CSS, or when asked to review/audit web UI. Default design baseline for new screens, plus container-first responsive rules, URL-first routing, scoped async loading, theme/i18n defaults, and applied UX laws.

Frontend & Design

Humanizer Kill Gpt

9

kargnas/skills

Runs a cross-language cleanup for writing tells shared by large frontier LLMs, not only GPT: English source constructs that survive other language translation and language-surface translationese. Use only when the user asks to remove AI/GPT tells from text (de-GPT, GPT 티, AI 티, 번역체 GPT, 자폐 말투 — colloquial shorthand for rigid or over-complete model prose, not a claim about autism).

AI, LLMs & Agents

Oss Finder

9

kargnas/skills

Finds battle-tested open-source repos, libraries, frameworks, CLI tools, or code on GitHub, ranked by README polish-days instead of stars. Also the shared GitHub code-search backend toolkit — rotating PAT pool, grep.app, Blackbird web index, BigQuery/GHArchive, and the code-search fallback chain. Use for 'find a library/framework/tool for X', 'battle-tested repo', GitHub-wide code search, or when `gh search code` rate-limits. Finding installable SKILL.md agent-skill packages goes to the skill-finder skill (it delegates its GitHub sweep here).

Git & Code Review

Shipreel

3

theBstar/shipreel

Turn a pull request into a short narrated walkthrough video (about two and a half minutes) with animated diagrams, code panels, optional screen recordings of the real app, captions, crossfade cuts and an ambient music bed. Runs locally with no paid services by default. Use when asked for a PR video, PR walkthrough, demo video of a change, or "make a shipreel".

Git & Code ReviewIn 1 list

Conventional Comments

9

milistu/agent-skills

Format review comments following the Conventional Comments standard. Use when writing code review comments, PR feedback, RFC reviews, peer reviews, or when the user asks for help with review comments.

Git & Code Review

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.