一键在 Manus 中运行任何 Skill

sessionexplain

星标5

分支3

更新时间2026年6月16日 23:12

Explain the intent behind source code by tracing it to the agent session transcript that created it. USE WHEN why does this function exist, what is this file for, why was this line added, explain this code's history, trace code to its originating conversation.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

N4M3Z

N4M3Z/forge-core

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

SessionExplain

Explain the intent behind source code by tracing it back to the original conversation where it was created. Backend commands live in @Entire.md. 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. "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 backend CLI is installed (see @Entire.md).
- If it is not, stop and tell the user how to install it.
Use a fast subagent 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 subagent to read the session transcript for that commit (command in @Entire.md).
- 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 a captured session (e.g., a manual commit)."

同仓库更多 Skills

同仓库

buildskill

N4M3Z/forge-core

Create and validate skills for forge modules. USE WHEN create skill, new skill, write skill, validate skill, check skill, skill structure, skill conventions.

2026-07-135

forgeskill

N4M3Z/forge-core

Create, validate, evaluate, and iterate skills for forge modules. USE WHEN create skill, new skill, write skill, validate skill, check skill, skill structure, skill conventions, test a skill, run skill evals, benchmark a skill, skill not triggering, optimize skill description. Not for adopting community skills (AdoptArtifact) or shipping artifacts downstream (PublishArtifact).

2026-07-135

buildrule

N4M3Z/forge-core

Create, validate, or place behavioral rules in forge modules. USE WHEN create rule, new rule, write rule, capture rule, add a rule, graduate a correction or convention to a rule, validate rule, rule conventions, where does this rule belong, or the user runs /Rule.

2026-07-135

initproject

N4M3Z/forge-core

Scaffold a workshop project: a VCS spine (git + jj colocate + entire + forge hooks), the private/public/assets flow layout with a .tlp manifest, a .claude/ that mounts the knowledge vault, and on-demand satellites (vault folder-note, data dir, private remote). USE WHEN starting a new project, initializing a folder for work, adding a vault note or data dir or remote to a project, archiving a project, or the user runs `project` / `atlas`.

2026-07-135

brainstorming

N4M3Z/forge-core

Collaborative ideation before implementation — explore context, clarify intent, propose approaches. USE WHEN starting creative work, new features, design decisions, or modifying behavior.

2026-07-135

designspec

N4M3Z/forge-core

Write a formal design spec from brainstorming output or requirements. USE WHEN design approved, write spec, formalize design, spec document.

2026-07-135

name	SessionExplain
version	0.1.0
description	Explain the intent behind source code by tracing it to the agent session transcript that created it. USE WHEN why does this function exist, what is this file for, why was this line added, explain this code's history, trace code to its originating conversation.
allowed-tools	Bash, Task
upstream	https://github.com/entireio/skills/blob/main/skills/explain/SKILL.md

SessionExplain

Explain the intent behind source code by tracing it back to the original conversation where it was created. Backend commands live in @Entire.md. 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. "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 backend CLI is installed (see @Entire.md).
- If it is not, stop and tell the user how to install it.
Use a fast subagent 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 subagent to read the session transcript for that commit (command in @Entire.md).
- 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 a captured session (e.g., a manual commit)."