git-context

Store and coordinate coding context inside Git repositories.

4|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/jxucoder/git-context --skill git-context-jxucoder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-context
Source: https://github.com/jxucoder/git-context/tree/main/skill
Command: npx skills add https://github.com/jxucoder/git-context --skill git-context-jxucoder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Store and coordinate coding context inside Git repositories. This capability helps teams preserve decisions, track tasks, and coordinate planning artifacts directly in the codebase, enabling offline-first collaboration.

Core Features & Use Cases

  • Embedded in Git: context lives in .git/ for a self-contained storage model.
  • Offline-first and distributed: works offline and is replicated with clones.
  • Multi-agent coordination: supports tasks, planning, and cross-agent workflows.
  • Local and Shared storage: choose between private notes and team-shared context.

Quick Start

Use git ctx to add a context entry locally, then push with the --shared flag to share with teammates.

Frequently Asked Questions about git-context

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

FAQPage Schema
How do I store coding context and notes directly inside a Git repository?

To store coding context in Git, you can use an offline-first, git-embedded storage model that saves decisions and notes inside the .git/ directory, keeping your context self-contained within the repository itself.

Can I coordinate tasks and planning across multiple agents using Git?

Yes, you can coordinate tasks and planning across multiple agents using Git by leveraging shared storage entries. This supports cross-agent workflows in both local and shared git environments for synchronized coding context.

Does Git work as an offline-first storage model for tracking development decisions?

Git works as an offline-first storage model for tracking development decisions by embedding context directly in the repository. Your notes and tasks are stored locally and automatically replicated whenever the repository is cloned.

What is the best way to share coding context and tasks with teammates in a distributed workflow?

The best way to share coding context in a distributed workflow is using a git-embedded approach with a shared storage flag. This pushes your local tasks and planning artifacts directly to the remote repository for team replication.

How do I separate private coding notes from team-shared context in a Git repository?

You separate private coding notes from team-shared context by using distinct local and shared storage commands. Local entries remain private to your workspace, while shared entries synchronize coding context with teammates through Git.