explain

Trace file:line references to originating prompts and sessions.

Updated Jun 2, 2026

Search Tags:#debugging #provenance #prompts #sessions #git-log #code-history

Ready to run

npx skills add https://github.com/chicago-joe/manymems --skill explain-chicago-joe

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Trace code provenance from prompts and sessions to explain why a function or line exists.

Core Features & Use Cases

Provenance tracing from file:line to prompt and session
Fallback to git log when provenance is unavailable
On-demand provenance search via the memory plugin
Debugging, auditing, and code-review use cases

Quick Start

Ask the AI to trace a file:line reference to identify the originating prompt and session.

Frequently Asked Questions about explain

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

FAQPage Schema

How do I trace code provenance from a file:line reference to its originating prompt?▼

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.

What happens when code provenance lookup is unavailable during a debugging session?▼

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.

Can I use code provenance tracing for auditing code across multi-user sessions?▼

Yes, code provenance tracing supports auditing by linking file:line references back to their originating prompts across multi-user sessions to verify code history.

How does tracing code history to prompts help with code reviews?▼

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.

What is the best way to find why a specific function exists in my codebase?▼

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.

Does code provenance tracing work without direct git log access?▼

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.