How do I install the Ce Sessions skill?

Run npx skillmds@latest add ci/ce-sessions in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ce Sessions safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ce Sessions?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ce Sessions free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ce Sessions?

ci (@ci) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ce Sessions by ci — Agent Skill

Name: Ce Sessions
Author: ci

Ce Sessions

Search and ask questions about your coding agent session history. Use when asking what you worked on, what was tried before, how a problem was investigated across sessions, what happened recently, or any question about past agent sessions. Also use when the user references prior sessions, previous attempts, or past investigations — even without saying 'sessions' explicitly.

ci c3937a5 2.1 KB Updated Sep 17, 2026

File contents

/ce-sessions

Search your session history.

Usage

/ce-sessions [question or topic]
/ce-sessions

Pre-resolved context

Repo name (pre-resolved): !common=$(git rev-parse --git-common-dir 2>/dev/null); if [ "$common" = ".git" ]; then basename "$(git rev-parse --show-toplevel 2>/dev/null)"; else basename "$(dirname "$common")"; fi

Git branch (pre-resolved): !git rev-parse --abbrev-ref HEAD 2>/dev/null

If the lines above resolved to plain values (a folder name like my-repo and a branch name like feat/my-branch), they are ready to pass to the agent. If they still contain backtick command strings or are empty, they did not resolve — omit them from the dispatch and let the agent derive them at runtime.

Execution

If no argument is provided, ask what the user wants to know about their session history. Use the platform's blocking question tool: AskUserQuestion in Claude Code (call ToolSearch with select:AskUserQuestion first if its schema isn't loaded), request_user_input in Codex, ask_user in Gemini, ask_user in Pi (requires the pi-ask-user extension). Fall back to asking in plain text only when no blocking tool exists in the harness or the call errors (e.g., Codex edit modes) — not because a schema load is required. Never silently skip the question.

Dispatch ce-session-historian with the user's question as the task prompt. Omit the mode parameter so the user's configured permission settings apply. Include in the dispatch prompt:

The user's question
The current working directory
The repo name and git branch from pre-resolved context (only if they resolved to plain values — do not pass literal command strings)

---name: ce-sessionsdescription: Search and ask questions about your coding agent session history. Use when asking what you worked on, what was tried before, how a problem was investigated across sessions, what happened recently, or any question about past agent sessions. Also use when the user references prior sessions, previous attempts, or past investigations — even without saying 'sessions' explicitly.---# /ce-sessionsSearch your session history.## Usage```/ce-sessions [question or topic]/ce-sessions```## Pre-resolved context**Repo name (pre-resolved):** !`common=$(git rev-parse --git-common-dir 2>/dev/null); if [ "$common" = ".git" ]; then basename "$(git rev-parse --show-toplevel 2>/dev/null)"; else basename "$(dirname "$common")"; fi`**Git branch (pre-resolved):** !`git rev-parse --abbrev-ref HEAD 2>/dev/null`If the lines above resolved to plain values (a folder name like `my-repo` and a branch name like `feat/my-branch`), they are ready to pass to the agent. If they still contain backtick command strings or are empty, they did not resolve — omit them from the dispatch and let the agent derive them at runtime.## ExecutionIf no argument is provided, ask what the user wants to know about their session history. Use the platform's blocking question tool: `AskUserQuestion` in Claude Code (call `ToolSearch` with `select:AskUserQuestion` first if its schema isn't loaded), `request_user_input` in Codex, `ask_user` in Gemini, `ask_user` in Pi (requires the `pi-ask-user` extension). Fall back to asking in plain text only when no blocking tool exists in the harness or the call errors (e.g., Codex edit modes) — not because a schema load is required. Never silently skip the question.Dispatch `ce-session-historian` with the user's question as the task prompt. Omit the `mode` parameter so the user's configured permission settings apply. Include in the dispatch prompt:- The user's question- The current working directory- The repo name and git branch from pre-resolved context (only if they resolved to plain values — do not pass literal command strings)

Frequently asked questions