cchistory

🥈Silver

cchistory tracks and retrieves your Claude Code session history, enabling quick access to previous commands and outputs. Operations teams benefit from faster debugging and workflow continuity. Integrates with Claude Code CLI, enhancing terminal-based development workflows.

10750Updated 2w ago

Intermediate30min to implementautomation

Saves ~15 min per use

Quick InstallView Source

git clone https://github.com/eckardt/cchistory.git

Works with:

Claude

Overview

About This Skill

How to Use

[{"step":"Identify the session or task. Use `cc history list` in the Claude Code CLI to list recent sessions, or specify a session ID if you know it.","tip":"Use `cc history list --filter \"error\"` to quickly find sessions with errors."},{"step":"Retrieve the history. Run `cc history get [SESSION_ID_OR_NAME]` to fetch the full session data, or use the prompt template above to summarize it directly.","tip":"For large sessions, use `cc history get [SESSION_ID] --limit 50` to limit the output to the most recent commands."},{"step":"Analyze the output. Look for patterns in errors, failed commands, or repeated operations. Use the summary table to identify key issues or successes.","tip":"Focus on timestamps to correlate commands with external events (e.g., deployments, API changes)."},{"step":"Take action. Based on the summary, either rerun commands, fix errors, or document the findings for your team.","tip":"Use `cc history export [SESSION_ID] --format json` to save the session data for further analysis or sharing."}]

Setup & Installation

Quick Install

No install command available. Check the GitHub repository for manual installation instructions.

Alternative Install (Git Clone)

git clone https://github.com/eckardt/cchistory

Requirements

Claude Code or compatible AI agent
Works with: Claude

Quick Start Guide

Install the Skill

Copy the install command above and run it in your terminal.

Open Your AI Agent

Launch Claude Code, Cursor, or your preferred AI coding agent.

Try It Out

Use the prompt template or examples below to test the skill.

Customize

Adapt the skill to your specific use case and workflow.

Usage Examples

Prompt Template

Retrieve and summarize the Claude Code session history from [SESSION_NAME_OR_ID]. Focus on commands related to [SPECIFIC_TASK_OR_ERROR]. Extract key outputs, errors, and timestamps for debugging. Format the summary as a markdown table with columns: Timestamp, Command, Output/Error, and Notes.

Example Output

Here’s a summary of your Claude Code session history for **Session ID: cc-20240515-1422** (focused on debugging a Python API integration issue):

| Timestamp          | Command                          | Output/Error                                                                 | Notes                          |
|--------------------|----------------------------------|------------------------------------------------------------------------------|--------------------------------|
| 2024-05-15 14:23:12 | `pip install requests`           | Successfully installed requests-2.31.0                                      | Dependency resolved            |
| 2024-05-15 14:25:07 | `python api_client.py test`      | `KeyError: 'API_KEY'`                                                        | Missing environment variable   |
| 2024-05-15 14:27:45 | `export API_KEY=your_key_here`   | Environment variable set                                                     | Fixed in next run              |
| 2024-05-15 14:29:10 | `python api_client.py test`      | `200 OK` with mock response                                                  | Integration test passed        |
| 2024-05-15 14:31:22 | `git commit -m "Fix API auth"`  | `On branch main: [new commit] Fix API auth (#123)`                            | Change tracked                 |

**Key Findings:**
1. The initial error was due to a missing `API_KEY` environment variable.
2. After setting the variable, the API integration test passed successfully.
3. The fix was committed to the repository as commit `#123`.

**Recommended Next Steps:**
- Add `API_KEY` to your `.env` file for persistence.
- Run the integration test again to confirm the fix in a clean environment.
- Share this summary with your team for context on the debugging process.