[delight] UX Analysis Report — 2026-07-27

[github-actions[bot]]

User Experience Analysis Report — 2026-07-27

Executive Summary

Today's analysis focused on:

• 2 documentation files
• 2 CLI commands
• 2 workflow message configurations
• 1 validation file

Overall Quality: ⚠️ Needs Minor Work

Key Finding: The Dev Hawk workflow messages use playful bird metaphors that undermine its professional CI monitoring role — a one-file update would immediately improve enterprise credibility.

---

Quality Highlights ✅

Playwright Reference Documentation

• File: docs/src/content/docs/reference/playwright.md
• What works well: Excellent mode comparison (CLI vs MCP), clear deprecation, inline YAML examples for every use case, and a practical wait-for-server pattern in the visual regression section.
• Quote: "CLI mode is recommended for all new workflows — it is token-efficient... avoids Docker overhead"

Validation Error Messages

• File: pkg/workflow/compiler_filters_validation.go
• What works well: Every error includes a corrective YAML snippet. newUnScopedPushError is exemplary — it explains why unscoped push is dangerous (feature-branch fan-out) then provides the exact fix.

---

Improvement Opportunities 💡

High Priority

Opportunity 1: Dev Hawk Workflow Messages — Tone Mismatch

• File: .github/workflows/dev-hawk.md
• Current State: Messages use bird metaphors throughout:
  • run-started: "🦅 Dev Hawk circles the sky! ... monitoring this {event_type} from above..."
  • run-success: "🦅 Hawk eyes report! ... completed reconnaissance. Intel delivered! 🎯"
  • run-failure: "🦅 Hawk down! ... The skies grow quiet..."
• Issue: Dev Hawk is a serious CI monitoring workflow that analyses failure root causes and creates Copilot tasks. The whimsical metaphors contrast with the analytical, enterprise-grade work the workflow performs.
• User Impact: Engineers investigating a CI failure see "Hawk down! The skies grow quiet" instead of a clear status — adding friction at the worst moment.
• Design Principle: Professional Communication

Medium Priority

Opportunity 2: Blog Quick Start URLs

• File: docs/src/content/docs/blog/2026-01-13-meet-the-workflows-campaigns.md
• Current State: Three Quick Start links use https://github.github.com/gh-aw/setup/quick-start/ — a hostname that differs from all other documentation links in the repo (/gh-aw/ relative paths or github.com/github/gh-aw).
• Issue: If github.github.com is not the live domain, these links 404 for new users trying to get started from the highest-profile blog post in the series (the finale).
• User Impact: New adopters following the post may hit dead links and abandon setup.
• Design Principle: Trust and Reliability

---

Files Reviewed

Documentation

• docs/src/content/docs/blog/2026-01-13-meet-the-workflows-campaigns.md — ⚠️ Needs Minor Work
• docs/src/content/docs/reference/playwright.md — ✅ Professional

CLI Commands

• gh aw compile — ✅ Professional (12 well-chosen examples, thorough flag docs)
• gh aw run — ✅ Professional (clear interactive-mode description, practical flags)

Workflow Messages

• .github/workflows/dev-hawk.md — ❌ Needs Significant Work (tone mismatch)
• .github/workflows/daily-fact.md — ✅ Professional (poetic style is intentional and consistent with purpose)

Validation Code

• pkg/workflow/compiler_filters_validation.go — ✅ Professional

---

Metrics

• Files Analyzed: 7
• Quality Distribution:
  • ✅ Professional: 5
  • ⚠️ Needs Minor Work: 1
  • ❌ Needs Significant Work: 1

---

🎯 Actionable Tasks

Task 1: Improve Dev Hawk Status Messages — .github/workflows/dev-hawk.md

File to Modify: .github/workflows/dev-hawk.md

Current Experience

The messages: block in the safe-outputs: section:

messages:
  footer: "> 🦅 *Observed from above by [{workflow_name}]({run_url})*{ai_credits_suffix}{history_link}"
  run-started: "🦅 Dev Hawk circles the sky! [{workflow_name}]({run_url}) is monitoring this {event_type} from above..."
  run-success: "🦅 Hawk eyes report! [{workflow_name}]({run_url}) has completed reconnaissance. Intel delivered! 🎯"
  run-failure: "🦅 Hawk down! [{workflow_name}]({run_url}) {status}. The skies grow quiet..."

Quality Issue

Design Principle: Professional Communication — messages should communicate state clearly and respect context.

Dev Hawk performs high-stakes work: analysing CI failures, correlating audit data with code diffs, and creating Copilot remediation tasks. When a developer receives a failure notification they need to act on immediately, "Hawk down! The skies grow quiet" adds unnecessary whimsy.

Proposed Improvement

Before:

messages:
  footer: "> 🦅 *Observed from above by [{workflow_name}]({run_url})*{ai_credits_suffix}{history_link}"
  run-started: "🦅 Dev Hawk circles the sky! [{workflow_name}]({run_url}) is monitoring this {event_type} from above..."
  run-success: "🦅 Hawk eyes report! [{workflow_name}]({run_url}) has completed reconnaissance. Intel delivered! 🎯"
  run-failure: "🦅 Hawk down! [{workflow_name}]({run_url}) {status}. The skies grow quiet..."

After:

messages:
  footer: "> 🦅 *Monitored by [{workflow_name}]({run_url})*{ai_credits_suffix}{history_link}"
  run-started: "🦅 [{workflow_name}]({run_url}) is analysing this {event_type}..."
  run-success: "🦅 [{workflow_name}]({run_url}) completed analysis successfully."
  run-failure: "🦅 [{workflow_name}]({run_url}) {status}. Review the comment on your PR for details."

Why This Matters

• User Impact: Developers triaging CI failures see a direct status with next-step guidance.
• Quality Factor: Professional Communication — message text matches the seriousness of the workflow's role.
• Frequency: Every Dev workflow completion on a copilot/* branch triggers this.

Success Criteria

• Changes made to .github/workflows/dev-hawk.md only
• run-failure message includes actionable next-step reference
• Metaphor language removed; 🦅 emoji retained as workflow identifier
• Quality rating improves from ❌ to ✅

Scope Constraint

• Single file only: .github/workflows/dev-hawk.md

---

Task 2: Fix Quick Start Links — docs/src/content/docs/blog/2026-01-13-meet-the-workflows-campaigns.md

File to Modify: docs/src/content/docs/blog/2026-01-13-meet-the-workflows-campaigns.md

Current Experience

Three occurrences of this URL:

https://github.github.com/gh-aw/setup/quick-start/

Quality Issue

Design Principle: Trust and Reliability — accurate links are foundational for new users acting on blog guidance.

The hostname github.github.com appears only in this file. All other documentation uses relative paths like /gh-aw/setup/quick-start/. If that subdomain is not the canonical live domain, these links 404 for every reader of the series finale post.

Proposed Improvement

Replace all three occurrences:

Before:

[Quick Start](https://github.github.com/gh-aw/setup/quick-start/)

After:

[Quick Start](/gh-aw/setup/quick-start/)

Why This Matters

• User Impact: New adopters arriving via this blog post can successfully navigate to setup instructions.
• Quality Factor: Trust and Reliability — a broken onboarding link directly reduces adoption.
• Frequency: This is the finale of a 19-part series — widely shared and linked.

Success Criteria

• Changes made to docs/src/content/docs/blog/2026-01-13-meet-the-workflows-campaigns.md only
• All three Quick Start URLs corrected to consistent relative paths
• Quality rating improves from ⚠️ to ✅

Scope Constraint

• Single file only: docs/src/content/docs/blog/2026-01-13-meet-the-workflows-campaigns.md

References:

• Workflow Run §30280564509

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• storage.googleapis.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "storage.googleapis.com"

See Network Configuration for more information.

📊 User experience analysis by Delight · sonnet46 · 67.7 AIC · ⌖ 5.64 AIC · ⊞ 8.5K · ◷

• expires on Jul 30, 2026, 7:41 AM UTC-08:00