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.

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplary short skill body: executable examples, a clear sequenced workflow with edge-case guidance, a verification checklist, and well-organized sections with no padding. It respects token budget while remaining fully actionable.

Dimension	Reasoning	Score
Conciseness	Lean and efficient: no concept over-explanation, every section (Quick start, Why, Workflow, Anti-patterns, Checklist) earns its place and assumes Claude's competence.	5 / 5
Actionability	Fully executable, copy-paste-ready commands covering the common cases — `git blame -L`, `git log -L :<function>:<file>`, `git log -n 1 -- <file>`, and the `memory_commit_lookup` call with a concrete SHA example.	5 / 5
Workflow Clarity	Three clearly sequenced steps, a verification checklist, and explicit edge-case handling for `commit: null`; the operation is read-only so no destructive validation loop is required.	5 / 5
Progressive Disclosure	No bundle files are needed; the body is well-organized into clear sections with a single one-level-deep, clearly signaled external reference (../_shared/TROUBLESHOOTING.md) and a See-also list of related skills.	5 / 5
	Total	20 / 20 Passed

Description

90%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, concrete description with explicit what/when structure and highly natural trigger phrases. Its only limitation is that it describes a single primary action rather than several, which caps specificity at the mid range.

Dimension	Reasoning	Score
Specificity	Names a single concrete action ('Trace a file, function, or line back to the agent session that produced its current commit') with three input variants, matching the '1-2 concrete actions, not comprehensive' anchor rather than the 'several specific actions' anchor at 4.	3 / 5
Completeness	Explicitly answers both what (trace a location back to its producing agent session) and when (concrete 'Use when...' trigger phrases), matching the top anchor.	5 / 5
Trigger Term Quality	Quotes natural phrases users actually say ('why is this code here', 'what was the agent doing when this changed', 'who wrote this') plus a general location-context case, giving comprehensive trigger coverage.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (commit-to-agent-session linking) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: rohitg00/agentmemory
Path: plugin/skills/commit-context/SKILL.md
Commit: 2d38daf

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.