git-context

Inspect git diffs, blame, logs, and notes to inform planning and debugging.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/reiserwang/Coding_Agent --skill git-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-context
Source: https://github.com/reiserwang/Coding_Agent/tree/main/.gemini/skills/git-context
Command: npx skills add https://github.com/reiserwang/Coding_Agent --skill git-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git history is a rich knowledge base — every commit, note, and diff encodes decisions, rationale, and evolution. This skill teaches agents to query git as context before planning, debugging, or reviewing code.

Core Features & Use Cases

  • Read git diff, blame, log, and notes to inform decisions before acting
  • Support debugging, planning, and code review by surfacing historical context
  • Use cases include starting a Conductor track, debugging regressions, reviewing changes, and resuming work

Quick Start

Ask the git-context skill to load relevant history and surface diffs, logs, and notes to inform your next action.

Frequently Asked Questions about git-context

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

FAQPage Schema
How do I use git history to provide context before debugging a regression?

Query git history to surface diffs, blame, logs, and notes as contextual input before debugging regressions. Inspecting these historical records encodes past decisions and rationale, informing your next action and isolating the root cause effectively.

What is the best way to review code changes using git diff and blame?

The best way to review code changes is querying git diff and blame to surface historical context. This approach reveals the evolution and rationale behind specific lines, ensuring your code review is informed by past decisions rather than isolated changes.

Can I load git log and notes when resuming work on a Conductor track?

Yes, you can load git log and notes when starting a Conductor track or resuming work. Querying this git history surfaces diffs and rationales as contextual input, allowing you to quickly recall past decisions and plan your next steps.

Does git-context work without external dependencies or components?

Git-context operates with no external dependencies or components. It directly queries your existing git history using commands like diff, blame, log, and notes to surface contextual input for planning, debugging, and code review.

When should I query git history as context before starting a task?

You should query git history as context before starting a Conductor track, debugging regressions, performing code reviews, or resuming work. Surface diffs, blame, logs, and notes to inform decisions and understand the rationale behind code evolution.