Add markdown formatting guidelines to daily-cli-performance workflow

[Copilot]

The daily-cli-performance workflow generates performance reports without formatting guidelines, resulting in inconsistent report structure. This adds explicit formatting instructions aligned with other reporting workflows.

Changes

• Added formatting guidelines section (5.1) instructing the agent to:

  • Use h3+ headers for proper hierarchy
  • Wrap detailed sections in <details> tags for progressive disclosure
  • Structure reports with critical info visible, details collapsible

• Updated issue template to follow guidelines:

  • h3/h4 headers instead of h1/h2
  • Wrapped "Detailed Performance Metrics" and "Additional Context" in collapsible sections
  • Added visual hierarchy with emojis

• Enhanced report generator script to output formatted markdown:

  • Generates report.md with proper header levels
  • Applies progressive disclosure to benchmark details and historical comparisons
  • Groups benchmarks by status (regressions, warnings, improvements)

Example

Before:

# Performance Regression Detected
## Benchmark: CompileSimpleWorkflow
...all content always visible...

After:

### 📊 Performance Regression Detected
#### Benchmark: CompileSimpleWorkflow
**Current Performance**: 150ms | **Historical**: 100ms | **Change**: +50%

<details>
<summary><b>📈 Detailed Performance Metrics</b></summary>
...expandable content...
</details>

Aligns with formatting patterns in daily-issues-report and audit-workflows.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[workflow-style] Normalize report formatting for daily-cli-performance</issue_title>
<issue_description>### Workflow to Update

Workflow File: .github/workflows/daily-cli-performance.md
Issue: This workflow generates performance reports but doesn't include markdown style guidelines

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."

2. Progressive Disclosure

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

Example:

<details>
<summary><b>Full Performance Details</b></summary>

[Long detailed content here...]

</details>

3. Report Structure

Suggest a structure like:

• Brief summary (always visible)
• Key performance metrics (always visible)
• Detailed benchmark results (in <details> tags)
• Historical comparisons (in <details> tags)
• Recommendations (always visible)

Design Principles (Airbnb-Inspired)

The updated workflow should create reports that:

1. Build trust through clarity: Most important info immediately visible
2. Exceed expectations: Add helpful context, trends, comparisons
3. Create delight: Use progressive disclosure to reduce overwhelm
4. Maintain consistency: Follow the same patterns as other reporting workflows

Example Reference

See workflows like daily-repo-chronicle, daily-issues-report, or audit-workflows for good examples of structured reporting with progressive disclosure.

Agent Task

Update the workflow file .github/workflows/daily-cli-performance.md to include the formatting guidelines above in the prompt instructions. Test the updated workflow to ensure it produces well-formatted reports.
Related to #11271

AI generated by Workflow Normalizer

• expires on Jan 31, 2026, 12:23 PM UTC

Comments on the Issue (you are @copilot in this section)

• Fixes [workflow-style] Normalize report formatting for daily-cli-performance #11650

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.