skills.rest
sebnow
sebnowCOMMUNITY
Explore all skills by this author →
Website𝕏@sebnowGitHub

tracing-knowledge-lineages

Traces decision lineage through git/jj logs, ADRs, and decision records.

8|Updated Dec 16, 2008
Search Tags:#git#architecture#refactoring#adr#traceability#jj#decision-history
One-click install
npx skills add https://github.com/sebnow/configs --skill tracing-knowledge-lineages-sebnow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tracing-knowledge-lineages
Source: https://github.com/sebnow/configs/tree/main/home-manager/agentic/skills/tracing-knowledge-lineages
Command: npx skills add https://github.com/sebnow/configs --skill tracing-knowledge-lineages-sebnow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Trace decision lineage through git/jj logs, commit messages, and decision records to avoid repeating failures and rediscover abandoned solutions.

Core Features & Use Cases

  • Trace history of decisions before refactoring or replacing patterns to preserve context.
  • Identify why a particular approach was chosen and when it became outdated.
  • Use ADRs, commit messages, and decision records to surface rationale and historical constraints.

Quick Start

Analyze your repository history to surface the rationale behind a recent change before executing a rewrite.

Frequently Asked Questions about tracing-knowledge-lineages

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

FAQPage Schema
How do I trace decision lineage from git logs before refactoring legacy code?▼

Trace decision lineage by searching git or jj commit histories, ADRs, and decision records to surface rationale behind architectural choices, preventing repeated failures during pattern replacement and modernization.

Why does outdated architecture need decision history tracing before replacement?▼

Decision history tracing identifies why an approach was chosen and when it became outdated, preventing you from repeating past failures or rediscovering abandoned solutions during refactoring and pattern replacement.

Can I use ADRs and commit messages to find abandoned solutions in my repository?▼

Yes, you can use ADRs, commit messages, and decision records to surface historical constraints and rationale, allowing you to rediscover abandoned solutions and preserve context before executing a rewrite.

What is the best way to prevent repeated failures during code modernization?▼

The best way to prevent repeated failures is analyzing repository history to surface decision lineage, summarizing insights from commit logs and decision records to activate historical context for future refactoring work.

When do I need to search commit histories and decision records for traceability?▼

You need to search commit histories and decision records during refactoring, pattern replacement, modernization, and when labels like legacy or outdated are used across code, architecture decisions, and changelog documentation.

Does this decision lineage tracing work with both git and jj version control logs?▼

Yes, decision lineage tracing works with both git and jj logs, searching commit histories alongside ADRs and decision records to summarize lineage insights for activation in future refactoring work.

Related Skills

Explore More Software Engineering Skills→
c-tomiokac-tomioka

adr-madr

Generate MADR-compliant architectural decision records from git logs, pull requests, or freeform text.

Community
Intermediate
robertpellonirobertpelloni
2

tracing-knowledge-lineages

Trace idea lineage through decision records and version history.

Community
Intermediate
windyskywindysky

moai-docs-generation

Generate documentation patterns from code for Sphinx, MkDocs, TypeDoc, and Nextra.

Community
Advanced
xenitV1xenitV1
132

architecture

Systematize requirements analysis and ADR documentation for architecture decisions.

Community
Basic