chronicle

Analyze Copilot session history for standup reports, usage tips, and session search.

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/az0512124155azz-sys/CodeForge --skill chronicle-az0512124155azz-sys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chronicle
Source: https://github.com/az0512124155azz-sys/CodeForge/tree/main/extensions/copilot/assets/prompts/skills/chronicle
Command: npx skills add https://github.com/az0512124155azz-sys/CodeForge --skill chronicle-az0512124155azz-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers lose track of what they accomplished across many Copilot chat sessions, making it hard to write standups, find past work, or understand how they use AI assistance. This Skill queries the Copilot session store to reconstruct activity, surface patterns, and answer questions about past sessions. ## Core Features & Use Cases - Standup Reports: Generates a formatted daily standup from the last 24 hours of sessions, grouped by branch and feature, with PR status checked via GitHub CLI or MCP tools. - Usage and Cost Tips: Analyzes prompting patterns, tool usage, token consumption (cloud DuckDB) or proxy signals like missing compactions (local SQLite) to produce personalized, data-grounded recommendations. - Session Search and Maintenance: Searches past sessions by keyword, file path, or PR/issue reference using FTS5 locally or ILIKE on cloud, plus reindexing and guidance for deleting session data. - Use Case: Before a morning standup, ask for a summary of yesterday's work and receive a grouped report of completed and in-progress features with linked PRs and session IDs. ## Quick Start Ask the assistant to generate a standup report from your Copilot session history for the last 24 hours.

Frequently Asked Questions about chronicle

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

FAQPage Schema
How do I generate a standup report from Copilot chat history?▼

Ask for a standup or daily summary and the skill queries the sessions table for the last 24 hours of activity, groups work by branch and feature, checks PR status via GitHub CLI or MCP tools, and formats results as Done and In Progress sections.

How do I search past Copilot sessions by keyword?▼

Request a session search with your keyword and the skill queries session summaries, conversation turns, file paths, and PR or issue references. Local storage uses the FTS5 search_index table while cloud storage uses ILIKE pattern matching with a default 7-day window.

Why is the copilot_sessionStoreSql tool not available?▼

The tool requires the github.copilot.chat.localIndex.enabled setting to be true in VS Code Settings. Enable this setting first, then the session store tool becomes available for querying and reindexing.

Does session history analysis work without cloud sync?▼

Yes, queries run against a local SQLite store containing sessions from the current device. However, per-event token usage data for cost analysis is only available on the cloud DuckDB backend, which requires enabling chat.sessionSync.enabled.

Can I delete my Copilot session history through this skill?▼

Deletion is intentionally not supported by the query tool to prevent accidental data loss. Use the Delete Session Sync Data command from the Command Palette to choose which sessions to remove from local storage and the cloud.

How do I reduce Copilot token costs based on my usage?▼

Ask for cost tips and the skill analyzes your interactive VS Code chat sessions for long uncompacted sessions, oversized pastes, premium model usage on routine tasks, and repeated file reads, then gives specific recommendations grounded in your actual data.