Skills
.Work. You
Rest

decision-archaeology

Community

Trace rationale behind code changes.

Software Engineering#read-only#commit-history#PR-traceability#code-rationale#git-blame#issue-trace
Authorntsk
Version1.0.0
Installs0

System Documentation

What problem does it solve?

This Skill helps you investigate why code was written a certain way by tracing decision history through git blame, commit logs, PRs, and issues to understand the reasoning behind code changes.

Core Features & Use Cases

  • Identify code and target lines: Locate the exact portion of code to understand context.
  • Trace introducing commits: Use git blame to find the commit that introduced changes.
  • Link PRs and issues: Check commit messages for references to PRs or issues to uncover discussions.
  • Summarize rationale: Produce a concise rationale of why a change was made.

Quick Start

Provide the target file path and, optionally, a line range to analyze. The Skill will generate a decision-archaeology report outlining the who, when, why of the change.

Dependency Matrix

Required Modules

None required

Components

references

💻 Claude Code Installation

Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.

Please help me install this Skill:
Name: decision-archaeology
Download link: https://github.com/ntsk/dotfiles/archive/main.zip#decision-archaeology

Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
View Source Repository

Agent Skills Search Helper

Install a tiny helper to your Agent, search and equip skill from 223,000+ vetted skills library on demand.