Generate context-aware code explanations from file content and git history.
npx skills add https://github.com/mbwsims/claude-universe --skill explain-mbwsims
Please help me install this Agent Skill. Skill: explain Source: https://github.com/mbwsims/claude-universe/tree/main/skills/explain Command: npx skills add https://github.com/mbwsims/claude-universe --skill explain-mbwsims
Developers often receive superficial code descriptions that explain only what a file does, leaving them without insight into why it was designed that way, its evolution, and hidden complexities.
Explain the module src/utils/helpers.ts.
High-intent search queries and answers about installing and using this skill.
Code explanation enriched with git history works by reading the target file, analyzing churn metrics and author contributions, and surfacing design decisions to explain why the code was designed that way and how it evolved.
Deep contextual code analysis provides insight into why a file was designed a certain way by combining code reading, git history integration, and optional quantitative metrics to highlight architecture and critical considerations before modification.
Yes, you can augment code analysis with lenskit metrics. When lenskit_analysis and lenskit_graph tools are available, the explanation optionally incorporates quantitative metrics and dependency-graph data to provide deeper insights.
Yes, read access to the file system and git repository is required to analyze code history. This allows the tool to read source files, extract git history, and optionally integrate lenskit metrics for quantitative insights.
To explain a specific module, apply the tool to the file path. It reads the target file, extracts purpose and internal structure, gathers git churn metrics, and produces a structured report highlighting purpose, architecture, and history.
joshka0Extract relevant code snippets from repository files using natural-language questions.
in-the-loop-labsFetch pair-review comments and apply code changes in local or PR contexts.
LeeJuOhVerify document claims against codebase and git history.
Keiji-MiyakeExtract development narratives from Git history and repository documentation.
