se-sessions

Search coding agent session history to explain past work and decisions.

Updated May 7, 2026
One-click install
npx skills add https://github.com/simonwjackson/pi-software-engineering --skill se-sessions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: se-sessions
Source: https://github.com/simonwjackson/pi-software-engineering/tree/main/skills/se-sessions
Command: npx skills add https://github.com/simonwjackson/pi-software-engineering --skill se-sessions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly surface and reason about your coding agent's past work, decisions, and investigations across sessions.

Core Features & Use Cases

  • Session history search: quickly locate past questions, attempts, and outcomes.
  • Context-aware recall: relate findings to current project work and branches.
  • Audit trail: provide an accessible narrative of past investigations across sessions and time.

Quick Start

Ask the agent to search your session history for a topic to surface past work, decisions, and investigations.

Frequently Asked Questions about se-sessions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I search my coding agent session history for past work and decisions?

Coding agent session history search allows you to query past questions, attempts, and outcomes across multiple sessions. It surfaces decisions and long-running plans by passing your question and repo context to a dedicated historian dispatch.

What is the best way to review past investigations across multiple coding agent sessions?

Reviewing past investigations across multiple coding agent sessions is handled by querying the session history to provide an accessible audit trail narrative. This context-aware recall relates past findings to your current project work and branches.

Does this agent history search tool work with my current Git branch context?

Yes, the agent history search works with your current Git branch context. It passes the current directory and repo context to a historian dispatch, enabling runtime derivation of branch information to relate findings to current project work.

When do I need to query session history for my coding agent?

You need to query coding agent session history when referencing prior sessions, attempts, or investigations across long-running plans. It quickly surfaces and reasons about past work, decisions, and outcomes to provide an accessible audit trail.

Can I use this session-history recall to audit decisions from long-running coding plans?

Yes, you can use session-history recall to audit decisions from long-running coding plans. It provides an accessible narrative of past investigations across sessions, allowing you to quickly locate past questions, attempts, and outcomes.