[workflow-style] Normalize report formatting for non-compliant workflows

[github-actions]

Workflow Style Normalization — Non-Compliant Reporting Workflows

The following report-generating workflows (active in the last 24 hours) don't fully follow the markdown style guidelines for headers, progressive disclosure, and report structure. Consolidating them here for a single pass of fixes.

Required changes for each workflow below:

• Add explicit instruction that report headers must start at ### (h3) or lower.
• Wrap long lists/details in <details><summary><b>...</b></summary> blocks for progressive disclosure.
• Reference the reporting skill (or equivalent structure guidance) so output follows a consistent, delightful report structure.

Workflow	File	Missing
Test Quality Sentinel	.github/workflows/test-quality-sentinel.md	header guidance, report structure
Impeccable Skills Reviewer	.github/workflows/impeccable-skills-reviewer.md	header guidance, report structure
Smoke Copilot	.github/workflows/smoke-copilot.md	header guidance, <details>, report structure
Smoke Codex	.github/workflows/smoke-codex.md	header guidance, <details>, report structure
Code Scanning Fixer	.github/workflows/code-scanning-fixer.md	header guidance, <details>, report structure
Copilot PR Prompt Pattern Analysis	.github/workflows/copilot-pr-prompt-analysis.md	header guidance, <details>, report structure
Daily Safe Output Tool Optimizer	.github/workflows/daily-safe-output-optimizer.md	header guidance, report structure
ESLint Monster	.github/workflows/eslint-monster.md	header guidance, <details>, report structure
Daily Compiler Quality Check	.github/workflows/daily-compiler-quality.md	header guidance, report structure
LintMonster	.github/workflows/lint-monster.md	header guidance, <details>, report structure
Sergo - Serena Go Expert	.github/workflows/sergo.md	header guidance, <details>, report structure
Step Name Alignment	.github/workflows/step-name-alignment.md	header guidance, <details>, report structure
The Great Escapi	.github/workflows/firewall-escape.md	header guidance, <details>
Issue Arborist	.github/workflows/issue-arborist.md	header guidance, <details>, report structure
Daily Sub-Agent Model Resolution Audit	.github/workflows/daily-model-resolution.md	header guidance, report structure
Sub-Issue Closer	.github/workflows/sub-issue-closer.md	header guidance, <details>, report structure
Draft PR Cleanup	.github/workflows/draft-pr-cleanup.md	header guidance, report structure
Squad Game Planner	.github/workflows/squad-game-planner.md	header guidance, <details>, report structure
Dev	.github/workflows/dev.md	header guidance, <details>, report structure

Example: Progressive Disclosure Pattern

### Findings Summary

3 issues found that need attention.

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

- [ ] Issue A: description of what needs fixing
- [ ] Issue B: description of what needs fixing
- [x] Issue C: already resolved

</details>

Good Reference Examples

• .github/workflows/daily-repo-chronicle.md — clear h3+ headers, <details> for long lists, structured report sections.
• .github/workflows/audit-workflows.md — consistent progressive disclosure and workflow-run link formatting.

Design Principles (per Style Guidelines)

• Trust through clarity: keep the key takeaway visible; push details into collapsible sections.
• User-focused: summarize before drilling into raw data/lists.
• Consistency: use the same header/details/structure pattern across all reporting workflows.

Suggested Next Steps

• Update each listed workflow's markdown prompt with h3+ header guidance
• Add <details>/<summary> progressive disclosure instructions where long content is generated
• Reference the reporting skill or equivalent structure guidance
• Recompile affected workflows (make recompile) after edits

Generated by 🔧 Workflow Normalizer · auto · 30.4 AIC · ⌖ 8.12 AIC · ⊞ 9.5K · ◷

• expires on Aug 24, 2026, 5:13 AM UTC-08:00

[github-actions]

🛑 Retry blocked — human review required

This topic already has prior Copilot pull requests that were closed without merging. Automatic re-dispatch is disabled to avoid spending another agent session on a blocked topic.

A maintainer should review the prior closed PRs, clarify the requirements, and then add a 'retry approved' comment (or remove the copilot-retry-blocked label) before this issue is reassigned.

🍪 Om nom nom by Issue Monster · gpt54 · 3.98 AIC · ⌖ 9.86 AIC · ⊞ 10.2K · ◷

[github-actions]

This issue was automatically closed because it expired on 2026-08-24T13:13:39.411Z.

Closed by Workflow