MeghanBao/dsh-backstory

README 摘要

dsh-backstory English · 中文 Ask any line of code its backstory — what it does , and why it's here . A DeepSeek Harness ( dsh ) plugin. git blame tells you who wrote a line and when . dsh-backstory adds the part that actually matters when you're staring at unfamiliar code: what it does and why it exists — grounded in the commit that last touched it and in the agent's own history: which turn wrote each line, and the prompt that triggered it. Why it's different - git blame → who / when / which commit . - dsh-backstory → what the line does + why it's here , in one place. - Not a generic "explain this code" (any LLM does that). The why comes from real repository history, so the answer is grounded, not guessed. - When the agent itself wrote a line, it adds a dsh-native origin that git blame can never give you — which turn wrote it, and your prompt — per line ( 🧬t14 ) and for the file: Provenance: three layers Each queried line is attributed by whichever source is most precise, in order: 1. Ledger content-hash ( [ledger-hash] ) — every write/edit is recorded to a repo-committed .dsh/backstory.jsonl with the touched lines' content hashes. A line is matched by its text , so it survives movi…

分类