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.
Best for Debugging complex issues wi…Works with GitHubLow risk
⌘source
- author
@EveryInc- language
- TypeScript
★15kstars
1.1kforks
Apr 18, 2026
✦overview.md
Key Features
- ·Search across all coding agent session history
- ·Ask questions about past investigations and attempts
- ·Understand what was tried before in previous sessions
- ·Reference prior work without explicit 'session' mentions
Use Cases
- →Recalling what coding approaches were attempted in previous debugging sessions
- →Understanding how a complex problem was investigated across multiple agent sessions
- →Reviewing recent work history when returning to a project after a break
- →Finding specific solutions or investigations from past sessions
Best for
- ✓Debugging complex issues with history
- ✓Team knowledge transfer
- ✓Project continuity
Not ideal for
- !Real-time code execution
- !One-time simple queries
FAQs
name
ce-sessions
description
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-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, request_user_input in Codex, ask_user in Gemini). If no question tool is available, ask in plain text and wait for a reply.
$install
1-click copynpx skills add EveryInc/compound-engineering-plugin --skill ce-sessionsSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
4/ 5
very goodClear and well structured, with only minor parts that might need a second read.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
4/ 5
highMostly actionable with clear steps; only a few small gaps remain.