git-expert

Analyze Git history and generate conventional commits with MCP tools.

2|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/nathanvale/side-quest-marketplace --skill git-expert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-expert
Source: https://github.com/nathanvale/side-quest-marketplace/tree/main/plugins/git/skills/git-expert
Command: npx skills add https://github.com/nathanvale/side-quest-marketplace --skill git-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Navigating complex Git history, crafting perfect commits, and understanding past changes can be daunting and time-consuming. This skill simplifies all Git operations, from exploring history to managing commits, making version control intuitive and efficient, so you can focus on coding.

Core Features & Use Cases

  • History Analysis: Search commit messages, code changes, and trace file evolution to understand when and why changes were made.
  • Smart Commits: Create well-formatted Conventional Commits, split large changes into atomic units, and handle pre-commit hooks gracefully.
  • Session Awareness: Track uncommitted work and create temporary "checkpoint" commits before risky operations, ensuring your work is always safe.
  • Use Case: Ask "What changed in the auth module recently?" and the skill will search your Git history to find relevant commits, or ask "Commit my changes" and it will help craft a conventional commit.

Quick Start

What changed in the 'auth' module recently?

Frequently Asked Questions about git-expert

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I search Git history to find when a specific change was introduced?

Search commits by message, author, or code content using Git history search to locate when changes were made. This skill analyzes commit logs and diffs to trace file evolution and identify the exact commit introducing or removing code.

What's the best way to write conventional commits?

Conventional commits follow a structured format (type, scope, description) that standardizes commit messages across projects. This skill generates well-formed conventional commits automatically and enforces the format to keep history clean and searchable.

How do I split large commits into atomic, focused changes?

Atomic commits isolate single logical changes, making history easier to review and revert if needed. This skill splits large changesets into smaller, focused commits while maintaining accurate authorship and commit messages.

Can I create checkpoint commits before risky Git operations?

Session-aware checkpoints are temporary commits that save your work before performing risky operations like rebases or force pushes. This skill tracks uncommitted work and creates checkpoints automatically, ensuring your changes are never lost.

How do I prevent secrets from being committed to Git?

Pre-commit hooks scan staged changes for sensitive data like API keys and credentials before commits are finalized. This skill manages hook configuration and prevents accidental secret exposure while maintaining commit workflow.

Does this work with repositories that have complex branching histories?

Yes. This skill maintains branch context and uses Git log commands to navigate complex histories across multiple branches. It traces authorship and changes across all branches to answer questions about your entire repository state.