skills.rest
carlosamesar
carlosamesarCOMMUNITY
Explore all skills by this author →
GitHub

git-archaeology

Extract blame and commit metadata for specific lines in Git repositories.

1|Updated Apr 7, 2026
Search Tags:#git#commit#tracking#version-control#blame
One-click install
npx skills add https://github.com/carlosamesar/framework-sdd --skill git-archaeology-carlosamesar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-archaeology
Source: https://github.com/carlosamesar/framework-sdd/tree/main/.opencode/skills/git-archaeology
Command: npx skills add https://github.com/carlosamesar/framework-sdd --skill git-archaeology-carlosamesar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides deterministic Git evidence for specific lines or file regions, enabling exact traceability of changes and authorship in codebases.

Core Features & Use Cases

  • Line-level blame analysis: Identify who last modified a line and when.
  • Commit metadata retrieval: Access detailed commit information associated with code changes.
  • Use Case: For incident investigation, review preparation, or verifying responsibility, use this Skill to obtain authoritative commit data about specific code regions.

Quick Start

Use the git-archaeology skill to find the author and commit details for line 42 in src/auth/handler.ts.

Frequently Asked Questions about git-archaeology

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

FAQPage Schema
How do I find who modified a specific line in a Git repository for accountability?▼

To find who modified a specific line in a Git repository, you extract blame and commit metadata. This identifies the author and timestamp of changes for incident investigation and code reviews.

What commit details can I retrieve for specific code regions during incident investigation?▼

Commit details for specific code regions include the author, timestamp, and exact commit metadata associated with the changes. This provides deterministic Git evidence for verifying responsibility.

Does Git blame analysis work on local repositories without remote access?▼

Git blame analysis works on local repositories without remote access. It requires Git installed locally and valid commit history to perform precise line-level and file region metadata extraction.

What's the best way to trace code history for a specific file region?▼

The best way to trace code history for a specific file region is performing precise blame extraction. This accesses detailed commit information to support incident investigation and review preparation.

Why do I need valid commit history for line-level blame analysis?▼

Valid commit history is needed for line-level blame analysis because the extraction relies on historical records. Without complete commit metadata, determining exact authorship and traceability of changes is impossible.

Related Skills

Explore More Software Engineering Skills→
i3ringiti3ringit
3

git-history-analyzer

Analyze git history to trace file evolution, contributors, and change patterns.

Community
Intermediate
FuzzdkkFuzzdkk
3

dfir-report

Consolidate DFIR findings into an executive and technical incident report.

Community
Advanced
Tony363Tony363
19

sc-git

Automate Git operations with Conventional Commits and MCP integrations.

Community
Advanced
nich2533nich2533
51

spice

Analyze Git history to predict future code states and development paths.

Community
Advanced