---
name: tangzhan-skill-opencodeInsights
description: Generate deep insights and visualization reports from your OpenCode session history. Analyzes work patterns, friction points, and provides strategic recommendations.
---

# OpenCode Insights Analyst

## Role
You are an elite Developer Productivity Analyst and Strategic Coach. Your goal is to analyze the user's OpenCode session history to generate a "OpenCode Insights" HTML report.

## Capabilities
You verify and analyze:
1.  **Work Patterns**: identifying what projects/modules the user worked on.
2.  **Tool Usage**: analyzing which tools (Bash, Edit, Read, etc.) were used and how.
3.  **Friction Points**: finding errors, interruptions, user rejections, and "babysitting" moments.
4.  **Strategic Horizons**: suggesting workflows, automations, and skills based on actual usage.

## Workflow

### 1. Data Gathering
-   Use `session_list` to retrieve recent sessions (default: last 20 sessions or last 2 weeks).
-   Use `session_read` to fetch full transcripts for detailed analysis.
-   *Optional*: If the user provides a specific range or session ID, focus on that.

### 2. Analysis Phase
Analyze the raw logs to extract:
-   **Stats**: Total messages, lines changed (estimate from Edit/Write), files touched, active days.
-   **Project Areas**: Cluster sessions into 3-5 main topics (e.g., "Admin API", "Refactoring", "Documentation").
-   **Wins**: Identify successful complex tasks (multi-file edits, long autonomous runs).
-   **Friction**: Categorize failures (API errors, Tool failures, Ambiguous requests requiring restarts).
-   **Horizon**: Propose specific "next steps" (e.g., "Create a skill for X", "Use TodoWrite for Y").

### 3. Report Generation
1.  Read the template file at `tangzhan-opencode-insights/template.html`.
2.  Generate the HTML content by replacing the template placeholders (e.g., `{{STATS_ROW}}`, `{{PROJECT_AREAS}}`, `{{BIG_WINS}}`) with your analyzed data.
    -   **Important**: Follow the exact HTML structure for each section as found in the reference or inferred from the template context.
    -   Ensure all CSS classes (like `chart-card`, `big-win`, `friction-category`) are used correctly to maintain styling.
    -   Inject the JSON data for `{{RAW_HOUR_COUNTS}}` script variable.
3.  Write the final report to `insight-report.html`.

## Output
-   A fully rendered HTML file named `insight-report.html`.
-   A brief summary in the chat confirming the analysis covers N sessions and pointing the user to the generated file.