[step-names] Align "Upload charts" step names and fix compound/ambiguous step names across workflows

[github-actions]

Step Name Alignment Issues

Found across multiple .github/workflows/*.lock.yml files.

Summary

Analysis of all .lock.yml files identified three categories of new step naming issues: a widespread inconsistency between "Upload charts" and "Upload generated charts" across 18 workflows, compound step names that violate single-responsibility naming, and inconsistent verbs for the lock file recompilation operation.

---

Issues Identified

1. [High Priority] Inconsistency: "Upload charts" vs "Upload generated charts"

The established pattern for upload steps is Upload (artifact). Across 18 workflows, two variants exist for the same operation:

Using "Upload charts" (6 workflows):

• audit-workflows.lock.yml
• daily-firewall-report.lock.yml
• daily-performance-summary.lock.yml
• portfolio-analyst.lock.yml
• prompt-clustering-analysis.lock.yml
• stale-repo-identifier.lock.yml

Using "Upload generated charts" (12 workflows):

• copilot-pr-nlp-analysis.lock.yml
• copilot-session-insights.lock.yml
• daily-code-metrics.lock.yml
• daily-copilot-token-report.lock.yml
• daily-issues-report.lock.yml
• daily-news.lock.yml
• daily-repo-chronicle.lock.yml
• github-mcp-structural-analysis.lock.yml
• org-health-report.lock.yml
• python-data-charts.lock.yml
• stale-repo-identifier.lock.yml (uses both!)
• weekly-issue-summary.lock.yml

Issue:
The word "generated" is redundant — charts are always generated before uploading. The established Upload (artifact) pattern, used consistently across all other upload steps (Upload Safe Outputs, Upload agent artifacts, Upload prompt artifact, etc.), does not include process-describing adjectives.

Note: stale-repo-identifier.lock.yml uses both variants in different jobs, which is especially inconsistent.

Suggested improvement:
Standardize on "Upload charts" across all workflows.

---

2. [Medium Priority] Compound Step Names Violating Single-Responsibility Naming

Three workflows use step names that describe two distinct operations joined by "and":

Current step names:

• daily-news.lock.yml: "Setup directories and check cache"
• release.lock.yml: "Setup environment and fetch release data"
• ci-doctor.lock.yml: "Pre-download CI failure logs and artifacts, apply heuristics"

Issue:
Step names should describe one action. Compound names obscure what the step does, make logs harder to scan, and the comma in the third example is especially unusual syntax for a step name. The "Pre-download" verb prefix in the third is also non-standard — the established prefix for preparatory operations does not exist in other step names.

Suggested improvements:

• "Setup directories and check cache" → "Setup working directories" (cache check is implied by the setup)
• "Setup environment and fetch release data" → "Setup release environment" (or split into two steps)
• "Pre-download CI failure logs and artifacts, apply heuristics" → "Download CI failure logs and artifacts" (drop the comma+clause)

---

3. [Medium Priority] Inconsistent Verbs: "Rebuild lock files" vs "Recompile workflows"

Two workflows performing the same conceptual operation — regenerating .lock.yml files from source .md workflows — use different verbs:

Current step names:

• ci-coach.lock.yml: "Rebuild lock files"
• daily-copilot-token-report.lock.yml: "Recompile workflows"

Issue:
The project glossary defines this process as Compilation: "Translating Markdown workflows (.md files) into GitHub Actions YAML format (.lock.yml files)". The verb "Recompile" aligns with the glossary term, while "Rebuild" does not. Neither workflow currently uses the most precise form.

Suggested improvement:
Standardize on "Recompile workflows" (aligned with the glossary's "Compilation" concept) for both workflows.

---

Agentic Task Description

To improve these step names:

1. Review the context — confirm the suggested names accurately describe each step's implementation
2. Apply changes — update step names in the source workflow .md files (not the .lock.yml files directly)
3. Recompile — run gh aw compile (workflow-name).md to regenerate each .lock.yml
4. Verify consistency — ensure updated workflows follow the Upload (artifact) and single-verb patterns

All affected source files

Issue 1 — Standardize to "Upload charts":
.github/workflows/copilot-pr-nlp-analysis.md, .github/workflows/copilot-session-insights.md, .github/workflows/daily-code-metrics.md, .github/workflows/daily-copilot-token-report.md, .github/workflows/daily-issues-report.md, .github/workflows/daily-news.md, .github/workflows/daily-repo-chronicle.md, .github/workflows/github-mcp-structural-analysis.md, .github/workflows/org-health-report.md, .github/workflows/python-data-charts.md, .github/workflows/stale-repo-identifier.md, .github/workflows/weekly-issue-summary.md

Issue 2 — Fix compound names:
.github/workflows/daily-news.md, .github/workflows/release.md, .github/workflows/ci-doctor.md

Issue 3 — Standardize recompile verb:
.github/workflows/ci-coach.md

Related Files

• Project glossary: docs/src/content/docs/reference/glossary.md
• Naming patterns cache: /tmp/gh-aw/cache-memory/step-name-alignment.json

Priority

This issue is High Priority due to the widespread "Upload charts" inconsistency spanning 18 workflows (including one using both variants).

---

AI generated by Step Name Alignment for daily maintenance

Generated by Step Name Alignment

• expires on Feb 25, 2026, 12:33 PM UTC