How do I install the Commit Context skill?

Run npx skillmds@latest add rohitg00/commit-context in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Commit Context safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Commit Context?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Commit Context free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Commit Context?

rohitg00 (@rohitg00) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Commit Context by rohitg00 — Agent Skill

Name: Commit Context
Rating: 4.2 (5 reviews)
Author: rohitg00

Commit Context

Trace a file, function, or line back to the agent session that produced its current commit. Use when the user asks "why is this code here", "what was the agent doing when this changed", "who wrote this", or wants context on a specific location in the codebase.

rohitg00 fa782ef 2.0 KB Updated Sep 9, 2026

File contents

The user wants commit context for: $ARGUMENTS

Quick start

git blame -L 40,52 src/auth/refresh.ts   # -> SHA 9a1b2c3d

memory_commit_lookup { "sha": "9a1b2c3d4e5f60718293a4b5c6d7e8f901234567" }

Expected output:

9a1b2c3 on main by dev: "rotate refresh tokens"
Linked session 7f3a9c2 "Auth refresh rework", 14 obs.

Why

Report only what git and the lookup return. When the lookup gives commit: null, the commit predates session linking; do not invent intent.

Workflow

Find the SHA: git blame -L <start>,<end> <file> for a line range; git log -L :<function>:<file> for a function; git log -n 1 -- <file> for a bare path.
Look it up: memory_commit_lookup { "sha": "<full-sha>" }.
Present the commit (sha, short sha, branch, author, message), the linked session(s) (id, project, started/ended, observation count, summary), and the importance >= 7 observations via memory_recall when available.

Anti-patterns

WRONG: lookup returns { "commit": null }, you narrate "the agent was refactoring auth" from the diff alone.

RIGHT: "This commit predates session linking, so there is no recorded agent session. From git show: it changed token rotation in refresh.ts."

Checklist

SHA came from git blame/log, not a guess.
commit: null reported as "predates linking", no fabricated session.
Session details quote the lookup response verbatim.
No intent claimed beyond what observations state.

Troubleshooting

See ../_shared/TROUBLESHOOTING.md if memory_commit_lookup is not available.

---name: commit-contextdescription: Trace a file, function, or line back to the agent session that produced its current commit. Use when the user asks "why is this code here", "what was the agent doing when this changed", "who wrote this", or wants context on a specific location in the codebase.--- The user wants commit context for: $ARGUMENTS ## Quick start ```bash git blame -L 40,52 src/auth/refresh.ts # -> SHA 9a1b2c3d ``` ```json memory_commit_lookup { "sha": "9a1b2c3d4e5f60718293a4b5c6d7e8f901234567" } ``` Expected output: ```text 9a1b2c3 on main by dev: "rotate refresh tokens" Linked session 7f3a9c2 "Auth refresh rework", 14 obs. ``` ## Why Report only what git and the lookup return. When the lookup gives `commit: null`, the commit predates session linking; do not invent intent. ## Workflow 1. Find the SHA: `git blame -L <start>,<end> <file>` for a line range; `git log -L :<function>:<file>` for a function; `git log -n 1 -- <file>` for a bare path. 2. Look it up: `memory_commit_lookup { "sha": "<full-sha>" }`. 3. Present the commit (sha, short sha, branch, author, message), the linked session(s) (id, project, started/ended, observation count, summary), and the importance >= 7 observations via `memory_recall` when available. ## Anti-patterns WRONG: lookup returns `{ "commit": null }`, you narrate "the agent was refactoring auth" from the diff alone. RIGHT: "This commit predates session linking, so there is no recorded agent session. From `git show`: it changed token rotation in refresh.ts." ## Checklist - SHA came from git blame/log, not a guess. - `commit: null` reported as "predates linking", no fabricated session. - Session details quote the lookup response verbatim. - No intent claimed beyond what observations state. ## See also - `commit-history`: list many agent-linked commits at once. - `recall`: dig deeper into the linked session's observations. ## Troubleshooting See ../_shared/TROUBLESHOOTING.md if `memory_commit_lookup` is not available.

Frequently asked questions