explain

Trace dependencies and call sites to explain code targets with code references.

1|1|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/laststance/skills --skill explain-laststance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: explain
Source: https://github.com/laststance/skills/tree/main/skills/explain
Command: npx skills add https://github.com/laststance/skills --skill explain-laststance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Explains code targets with deep, introspective reasoning, revealing how and why decisions were made to improve understanding and auditability.

Core Features & Use Cases

  • Introspection markers: Makes reasoning steps visible throughout explanations to improve clarity.
  • Code-aware analysis: Reads actual source code and consults official docs to validate behavior.
  • Education and audits: Useful for code reviews, learning, and knowledge transfer within teams.

Quick Start

Provide a target (code/file/concept) and I will generate a deep, introspective explanation.

Frequently Asked Questions about explain

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

FAQPage Schema
How do I explain code logic and trace dependencies for a complex function?

To explain code logic, this Skill identifies the target type and gathers its source context, tracing imports and call sites to build an accurate mental model of how the code works within its ecosystem.

What is the best way to generate documentation for code reviews and audits?

Generating documentation for code reviews is done by reading actual source code and consulting official docs, producing a structured explanation with core insights, decisions, and concrete code references for auditability.

How does introspection help with analyzing unfamiliar source code?

Introspection helps analyzing unfamiliar source code by making reasoning steps visible throughout the explanation, clarifying how and why decisions were made to improve understanding and knowledge transfer.

Can I use this to explain a specific file, class, or concept in my codebase?

Yes, you can explain a specific file, class, or concept by providing the target, and the analysis will trace dependencies and call sites to generate a deep, introspection-rich explanation.

Does code explanation work without writing custom prompts for different target types?

Code explanation works automatically without custom prompts by identifying the target type, whether a file, function, class, or concept, and gathering the necessary source context to validate behavior.

Why should I use transparent reasoning for code analysis instead of standard documentation?

Transparent reasoning for code analysis reveals how and why decisions were made, providing deeper introspection and auditability than standard documentation, which is crucial for team learning and knowledge transfer.