Explain

Explains the intent behind source code by finding original session transcripts. Use explain with a function, file, or line of code to understand why it exists.

240 stars 28 forksSoftware Development Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add entireio/skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add entireio/skills --skill explain
Manual install
git clone --depth 1 https://github.com/entireio/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/explain ~/.claude/skills/explain

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Explain Intent

Explain the intent behind source code by tracing it back to the original conversation where it was created. Works with:

- **Functions** — Why does this function exist? What problem was it solving?
- **Files** — What's the purpose of this file? What requirements drove its creation?
- **Line changes** — Why was this specific line added or modified?

## Response Format

Begin the first response to this skill invocation with the line:

`Entire Explain:`

followed by a blank line, then the content.

- Apply the header to the **first response of the invocation only.** Do not re-print it on follow-up turns within the same invocation (e.g. after the user answers a clarifying question).
- Do **not** include the header on error or early-exit responses (e.g. "Entire CLI is required but not installed", "this file is not tracked by git", "no session transcript was found for this commit"). The header's presence should signal that the skill ran and produced real output.

## Process

1. Verify the `entire` CLI is installed by running `entire version`.
   - If the command is not found, stop and tell the user: "The Entire CLI is required but not installed. Install it from https://docs.entire.com/installation and try again."
2. If the user named a symbol without a file or line (e.g. "explain parseConfig") and the Entire Graph plugin is installed (`entire graph version` exits 0), find its definition first:

   ```bash
   entire graph def <Name> --repo . --head
   ```
Read the full skill on GitHub

Details

Skill name
explain
Path
skills/explain/SKILL.md
License
MIT
Repo updated
15 November 2026

FAQ

What does the Explain skill do?

Explains the intent behind source code by finding original session transcripts. Use explain with a function, file, or line of code to understand why it exists.

How do I install the Explain skill?

Claude Code plugin: /plugin marketplace add entireio/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Explain popular?

It lives in entireio/skills, which has 240 GitHub stars and 28 forks.

Related skills

Address Findings

240

entireio/skills

Address the review findings posted on an Entire trail: fetch the trail's open findings, fix the code, and resolve them on the trail. Use when the user gives a trail URL or number and asks to address, fix, or resolve its findings or review comments. Not for local diff review — that is the `review` skill.

Software Development28

Recall

240

entireio/skills

Use when the user describes a task and wants to know whether something similar has been done before, then turn the closest prior session into a task playbook. Triggers on phrases like "have we done this before", "recall how we did X", "find similar work", "any precedent for", "has anyone solved", "is there a template for", and "how did we do this last time

Productivity & Notes28

Replay

240

entireio/skills

Use when the user wants to step through a feature's checkpoints chronologically, pausing at each step to ask questions. Triggers on phrases like "replay <feature>", "walk me through how X was built", "show me the journey of", "step me through how Y was implemented", and "replay the last week

Other28

Releasing Clickup CLI

132

krodak/clickup-cli

Publishes a new version of clickup-cli to npm, updates Homebrew tap, writes release notes, and syncs the agent skill. Use when releasing a new version, bumping version, or verifying a release.

Software DevelopmentIn 1 list21

Databricks Zerobus Ingest

407

databricks/databricks-agent-skills

Push records from apps, services, devices, or scripts directly into Unity Catalog Delta tables with Zerobus Ingest: SDKs (Python, TypeScript, Go, Java, Rust, C++, .NET), REST, OTLP, MQTT, Arrow Flight, or Apache Kafka-compatible producer APIs, with no message bus to run. Use to stream events, telemetry, logs, IoT data, CDC, or columnar batches into Databricks in near real time; connect existing collectors and log shippers (OpenTelemetry, Debezium, Vector, Telegraf, Cribl); replace a message bus that only feeds the lakehouse; or debug Zerobus auth, schema, throughput, or delivery issues.

Software Development103

Spark Python Data Source

407

databricks/databricks-agent-skills

Build custom Python data sources for Apache Spark using the PySpark DataSource API — batch and streaming readers/writers for external systems. Use this skill whenever someone wants to connect Spark to an external system (database, API, message queue, custom protocol), build a Spark connector or plugin in Python, implement a DataSourceReader or DataSourceWriter, pull data from or push data to a system via Spark, or work with the PySpark DataSource API in any way. Even if they just say "read from X in Spark" or "write DataFrame to Y" and there's no native connector, this skill applies.

Software Development103

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.