Run any Skill in Manus with one click

explain

Stars203

Forks11

UpdatedMay 5, 2026 at 18:06

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

entireio

entireio/skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	explain
description	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.
argument-hint	<function, file, or line>

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

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://entire.io/docs/cli and try again."
Use a Haiku agent to identify the commit that introduced the code via git blame or git log.
- If the file is not tracked by git, stop and tell the user: "This file is not tracked by git, so I can't trace its history."
- If git blame returns no useful result (e.g., the code is uncommitted), stop and tell the user: "This code hasn't been committed yet, so there's no history to trace."
Use a Sonnet agent to read the session transcript via entire explain --no-pager --commit COMMIT_SHA.
- If the command fails or returns no transcript, stop and tell the user: "No session transcript was found for this commit. It may have been created outside of an Entire session (e.g., a manual commit)."

More from this repository

same repository

entireio/skills

Use when the user wants to find prior work, checkpoints, or agent conversations by topic, repo, branch, author, or recent time window, or to search code content across repositories

2026-07-10203

address-findings

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.

2026-06-30203

using-entire

entireio/skills

Use for any codebase exploration or understanding task — reads historical intent from Entire checkpoints instead of guessing. Orchestrates other Entire skills to give the agent provenance-backed answers about code.

2026-06-20203

teach

entireio/skills

Use when a developer wants a topic-focused guided lesson built from canonical checkpoints, not a whole-repo overview. Triggers on phrases like "teach me <topic>", "teach me how this repo handles", "how does <topic> work in this repo", "give me a lesson on", "school me on", and "I need to learn about"

2026-06-04203

review

entireio/skills

Review code changes on the current branch using checkpoint transcript context to understand developer intent before auditing the diff. Use when the user asks for a code review, wants to review branch changes, or asks to audit recent work before merging.

2026-06-01203

recall

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"

2026-05-29203

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

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://entire.io/docs/cli and try again."

Use a Haiku agent to identify the commit that introduced the code via git blame or git log.

If the file is not tracked by git, stop and tell the user: "This file is not tracked by git, so I can't trace its history."
If git blame returns no useful result (e.g., the code is uncommitted), stop and tell the user: "This code hasn't been committed yet, so there's no history to trace."

Use a Sonnet agent to read the session transcript via entire explain --no-pager --commit COMMIT_SHA.

If the command fails or returns no transcript, stop and tell the user: "No session transcript was found for this commit. It may have been created outside of an Entire session (e.g., a manual commit)."