[workflow-style] Normalize report formatting for copilot-session-insights

[github-actions]

Workflow File: .github/workflows/copilot-session-insights.md

This workflow analyzes Copilot session data and generates insight reports but doesn't include markdown style guidelines, which can lead to inconsistent formatting and poor readability.

Required Changes

Update the workflow prompt to include these formatting guidelines:

1. Header Levels

Add instruction: "Use h3 (###) or lower for all headers in your report to maintain proper document hierarchy."

The discussion/issue title serves as h1, so all content headers should start at h3:

• Use ### for main sections (e.g., "### Session Analysis", "### Usage Patterns")
• Use #### for subsections (e.g., "#### Command Distribution", "#### Error Patterns")
• Never use ## (h2) or # (h1) in the report body

2. Progressive Disclosure

Add instruction: "Wrap long sections in <details><summary><b>Section Name</b></summary> tags to improve readability and reduce scrolling."

Use collapsible sections for:

• Detailed session logs and transcripts
• Full command histories
• Verbose error messages and stack traces
• Complete user interaction patterns

Example:

<details>
<summary><b>Complete Session Logs</b></summary>

[Detailed session-by-session logs...]

</details>

3. Report Structure

Suggest a structure like:

1. Brief overview (always visible): Total sessions analyzed, key insights
2. Key metrics (always visible): Usage stats, success rates, common patterns
3. Detailed session analysis (in <details> tags): Per-session breakdowns, full logs
4. Recommendations (always visible): Actionable improvements for user experience

Design Principles (Airbnb-Inspired)

The updated workflow should create reports that:

1. Build trust through clarity: Most important insights immediately visible
2. Exceed expectations: Add trends, comparisons, contextual analysis
3. Create delight: Use progressive disclosure to make complex data digestible
4. Maintain consistency: Follow the same patterns as other reporting workflows

Example Reference

See workflows like daily-repo-chronicle.md or audit-workflows.md for good examples of structured reporting.

Agent Task

Update the workflow file .github/workflows/copilot-session-insights.md to include the formatting guidelines above. Test to ensure well-formatted reports.

AI generated by Workflow Normalizer

• expires on Feb 9, 2026, 12:31 PM UTC