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

[github-actions]

Workflows to Update

The following workflows generate reports but don't comply with the project's markdown style guidelines:

Workflow File	Issues Found
.github/workflows/daily-function-namer.md	Uses h1 (# 🏷️ Go Function Rename Plan) in issue body instead of h3 or lower

Required Changes

.github/workflows/daily-function-namer.md

The issue body template starts with an h1 heading:

# 🏷️ Go Function Rename Plan

Change to h3 to comply with the style guidelines:

### 🏷️ Go Function Rename Plan

Also add explicit formatting instruction near the issue creation step:

Use h3 (###) or lower for all headers in the issue body. Never use h1 (#) or h2 (##) — these are reserved for the issue title.

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 and examples
3. Maintain consistency: Follow the same patterns as other reporting workflows (e.g., daily-otel-instrumentation-advisor, agent-performance-analyzer)

Compliance Summary

Of the 17 active reporting workflows reviewed from the last 24 hours:

• ✅ 16 workflows follow the h3+ header guidelines (explicitly or implicitly)
• ❌ 1 workflow uses h1 in its issue body template

View Full Compliance Review

Workflow	Status	Notes
agent-performance-analyzer	✅ Compliant	Explicit h3 guidelines
api-consumption-report	✅ Compliant	Explicit h3 guidelines
prompt-clustering-analysis	✅ Compliant	Uses ### in templates
daily-otel-instrumentation-advisor	✅ Compliant	Explicit h3 guidelines
ab-testing-advisor	✅ Compliant	Explicit h3 guidelines
test-quality-sentinel	✅ Compliant	Explicit h3 guidelines
daily-function-namer	❌ Non-compliant	h1 in issue body
daily-doc-updater	✅ Compliant	Uses ### in templates
claude-code-user-docs-review	✅ Compliant	Explicit h3 guidelines
auto-triage-issues	✅ Compliant	Explicit h3 guidelines
design-decision-gate	✅ Compliant	ADR file (h1 appropriate); comments use ###
mattpocock-skills-reviewer	✅ Compliant	Uses ### in output template
pr-sous-chef	✅ Compliant	Operational, no structured reports
stale-pr-cleanup	✅ Compliant	Operational, no structured reports
draft-pr-cleanup	✅ Compliant	Operational, no structured reports
instructions-janitor	✅ Compliant	Creates PRs, not issue reports
terminal-stylist	✅ Compliant	Uses shared audit base

Agent Task

Update .github/workflows/daily-function-namer.md to change the issue body template's h1 to h3, and add explicit formatting guidelines near the issue creation step.

Generated by 🔧 Workflow Normalizer · ● 10.1M · ◷

• expires on May 17, 2026, 1:12 PM UTC