reflect-by-history

Analyze past IDE session history to identify recurring patterns and propose improvements.

Updated May 16, 2026

Search Tags:#pattern detection #project optimization #session history #codebase improvement #IDE analysis

Ready to run

npx skills add https://github.com/korchasa/flowai-plugins --skill reflect-by-history

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reflect-by-history
Source: https://github.com/korchasa/flowai-plugins/tree/main/plugins/flowai/skills/reflect-by-history
Command: npx skills add https://github.com/korchasa/flowai-plugins --skill reflect-by-history

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill allows users to review and analyze past IDE sessions to identify recurring patterns, systemic issues, and suggest improvements to project primitives like rules, skills, hooks, and documentation.

Core Features & Use Cases

Session History Analysis: Analyze historical IDE session transcripts to identify recurring behavioral patterns and systemic issues.
Pattern Detection: Find recurring errors, repeated manual workflows, ad-hoc decisions, unchecked invariants, underused primitives, and missing knowledge.
Fix Proposals: Classify potential fixes into rules, skills, commands, hooks, project docs, or code changes.
User-Specific Scope: Customize the scope of analysis based on user request, such as last few sessions, single session, or trend analysis.

Quick Start

Use the 'reflect-by-history' skill to analyze the last 10 sessions from your Claude Code IDE and propose improvements.

Frequently Asked Questions about reflect-by-history

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

FAQPage Schema

How do I analyze IDE session history to find recurring codebase patterns?▼

You can analyze IDE session history by reviewing past transcripts to detect recurring errors and repeated manual workflows. This skill processes your Claude Code, Cursor, or OpenCode sessions to identify systemic issues and propose targeted project improvements.

What is session history pattern detection for project optimization?▼

Session history pattern detection finds recurring errors, ad-hoc decisions, and unchecked invariants in your IDE transcripts. It classifies these patterns to suggest fixes like new rules, skills, hooks, or documentation updates for your codebase.

Can I use session history analysis with Cursor or OpenCode IDEs?▼

Yes, session history analysis supports Claude Code, Cursor, and OpenCode IDEs. The tool requires access to your IDE session history and an understanding of project primitives to accurately propose codebase improvements.

How do I get fix proposals for repeated manual workflows in my IDE?▼

To get fix proposals for repeated manual workflows, analyze your session history to identify the pattern. The skill then classifies potential fixes into rules, skills, commands, hooks, project docs, or direct code changes.

What's the best way to review past sessions for underused project primitives?▼

Reviewing past sessions for underused primitives requires analyzing historical IDE transcripts to find missing knowledge and ad-hoc decisions. This skill scopes the analysis to your requested sessions and proposes documentation or rule updates.

Does session history analysis work for a single session or trend analysis?▼

Session history analysis works for both single sessions and trend analysis. You can customize the scope based on your request, such as analyzing the last 10 sessions or focusing on a specific historical IDE transcript.