From e4e9e08013e6d77b966f9477582535859c3b0ab8 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Sat, 9 May 2026 21:04:36 +0000 Subject: [PATCH] [caveman] Trim report.md verbosity Apply caveman optimization: cut redundant lead-ins and the fluffy "Design Principles" section. All schema/structural guidance preserved. Co-Authored-By: Claude Opus 4.7 (1M context) --- .github/aw/report.md | 23 +++++------------------ 1 file changed, 5 insertions(+), 18 deletions(-) diff --git a/.github/aw/report.md b/.github/aw/report.md index 4fa1fb2d1f1..237b24841b9 100644 --- a/.github/aw/report.md +++ b/.github/aw/report.md @@ -40,23 +40,18 @@ safe-outputs: ### Header Levels -**Use `###` or lower for all headers in your report to maintain proper document hierarchy.** - -When creating GitHub issues or discussions: -- Use `###` (h3) for main sections (e.g., `### Test Summary`) -- Use `####` (h4) for subsections (e.g., `#### Device-Specific Results`) -- Never use `##` (h2) or `#` (h1) in reports — these are reserved for titles +- Use `###` (h3) for main sections — e.g., `### Test Summary` +- Use `####` (h4) for subsections — e.g., `#### Device-Specific Results` +- Never use `##` (h2) or `#` (h1) — those are reserved for titles ### Progressive Disclosure -**Wrap detailed content in `
Section Name` tags to improve readability and reduce scrolling.** - -Use collapsible sections for: +Wrap detailed content in `
Section Name` tags. Use for: - Verbose details (full logs, raw data) - Secondary information (minor warnings, extra context) - Per-item breakdowns when there are many items -Always keep critical information visible (summary, critical issues, key metrics). +Keep critical information visible (summary, critical issues, key metrics). ### Report Structure Pattern @@ -65,14 +60,6 @@ Always keep critical information visible (summary, critical issues, key metrics) 3. **Details**: Use `
Section Name` for expanded content 4. **Context**: Add helpful metadata (workflow run, date, trigger) -### Design Principles - -Reports should: -- **Build trust through clarity**: Most important info immediately visible -- **Exceed expectations**: Add helpful context like trends, comparisons -- **Create delight**: Use progressive disclosure to reduce overwhelm -- **Maintain consistency**: Follow patterns across all reports - ### Example Report Structure ```markdown