Trace file:line references to originating prompts and sessions.
npx skills add https://github.com/chicago-joe/manymems --skill explain-chicago-joe
Please help me install this Agent Skill. Skill: explain Source: https://github.com/chicago-joe/manymems/tree/main/plugin/skills/explain Command: npx skills add https://github.com/chicago-joe/manymems --skill explain-chicago-joe
Trace code provenance from prompts and sessions to explain why a function or line exists.
Ask the AI to trace a file:line reference to identify the originating prompt and session.
High-intent search queries and answers about installing and using this skill.
Trace code provenance by supplying a file:line reference to retrieve the originating session and prompt, using the memory plugin to explain why the code exists.
When code provenance is unavailable, the system automatically falls back to executing a git log query to retrieve historical context for the targeted file and line.
Yes, code provenance tracing supports auditing by linking file:line references back to their originating prompts across multi-user sessions to verify code history.
Tracing code history to prompts helps code reviews by revealing the exact session and intent that generated a function, clarifying its purpose and validating its implementation.
To find why a function exists, request a provenance trace using the file:line reference to locate the exact prompt and session that authored the code.
Code provenance tracing relies on on-demand provenance search via the memory plugin first, only falling back to git log if the provenance data is unavailable.
chicago-joeCorrelate commits with provenance data to explain code changes.
entireioCross-references Git branch diffs with developer checkpoint transcripts to identify mismatches between intended and actual code changes.
StrategicMilkTrace git history to uncover design decisions and regressions.
berkcangumusisikExplain code line origins using git blame and commit history.
