When should I use the Knowledge Lineage skill?

You should use it before abandoning current approaches, when questioning why a specific 'best practice' exists, or when evaluating a 'new' idea that might actually be a revival of a previously attempted pattern.

How does this skill help with legacy codebases?

It prevents developers from removing seemingly overcomplicated code that was actually implemented to solve specific historical edge cases, ensuring that 'simplification' doesn't re-introduce old bugs.

Can this skill help justify modernizing a stack?

Yes, by performing a Context Change analysis, it can identify if previous failures occurred due to constraints that no longer exist, such as outdated browser limitations or lack of specific tooling.

What is decision archaeology?

Decision archaeology is the systematic process of searching through historical records like Architecture Decision Records (ADRs), Git logs, and conversation history to understand the constraints and motivations behind a specific technical choice.

Knowledge Lineage Tracing

Name: Knowledge Lineage Tracing
Author: hameed0342j

byhameed0342j

0•

学習とドキュメンテーション

Analyzes the evolution of technical decisions and historical context to prevent repeating past mistakes and rediscover proven solutions.

Tracing Knowledge Lineages is a specialized capability that empowers developers to perform "decision archaeology" within their codebase. By systematically analyzing Git history, Architecture Decision Records (ADRs), and past discussions, it helps Claude understand the original intent behind current implementations and the reasons why previous approaches were abandoned. This skill is essential when evaluating major architectural changes, proposing new solutions that might be revivals of old patterns, or simply trying to understand the "why" behind complex legacy codebases, ensuring that future progress is built on a foundation of historical wisdom rather than ignorance.

主な機能

01Decision Archaeology: Investigates ADRs and Git logs to uncover the original intent behind code.

02Revival Detection: Identifies if new ideas are rebrands of older paradigms to leverage existing lessons.

030 GitHub stars

04Paradigm Shift Mapping: Documents the gains and losses during major architectural transitions.

05Failed Attempt Analysis: Evaluates why previous solutions failed to see if modern context makes them viable.

06Historical Search Strategies: Utilizes specialized Git and grep patterns to find specific decision contexts.

ユースケース

01Before proposing a total rewrite or replacement of a core system component.

02Onboarding onto a complex legacy project with significant technical debt.

03When evaluating if a previously discarded technology is now viable due to context changes.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add hameed0342j/svh tracing-knowledge-lineages

For use in Claude.ai and ChatGPT

主な機能

01Decision Archaeology: Investigates ADRs and Git logs to uncover the original intent behind code.

02Revival Detection: Identifies if new ideas are rebrands of older paradigms to leverage existing lessons.

030 GitHub stars

04Paradigm Shift Mapping: Documents the gains and losses during major architectural transitions.

05Failed Attempt Analysis: Evaluates why previous solutions failed to see if modern context makes them viable.

06Historical Search Strategies: Utilizes specialized Git and grep patterns to find specific decision contexts.

ユースケース

01Before proposing a total rewrite or replacement of a core system component.

02Onboarding onto a complex legacy project with significant technical debt.

03When evaluating if a previously discarded technology is now viable due to context changes.