Step Name Alignment Issues
Found in:
.github/workflows/super-linter.lock.yml (line 1290).github/workflows/smoke-workflow-call.lock.yml (line 171).github/workflows/smoke-workflow-call-with-inputs.lock.yml (line 168)
Summary
Two step names lack the imperative verb required by the established naming convention. All peer steps in this codebase use an action verb as the first word (e.g., "Run linter", "Print firewall logs"), but these two steps omit the verb entirely.
Issues Identified
1. [Medium Priority] Missing verb: "Super-linter" → "Run super-linter"
Current step name:
super-linter.lock.yml line 1290: Super-linter
Step uses: super-linter/super-linter@9e863354e3ff62e0727d37183162c4a88873df41
Issue:
The step name is just the tool name with no imperative verb. The established pattern requires a verb: compare with "Run unit tests", "Run linter", "Run stale-repos tool", "Run compile with security tools".
Suggested improvement:
"Super-linter" → "Run super-linter"
Source file: .github/workflows/super-linter.md line 39
2. [Medium Priority] Missing verb: "Cross-repo setup guidance" → "Print cross-repo setup guidance"
Current step name (compiler-generated):
smoke-workflow-call.lock.yml line 171smoke-workflow-call-with-inputs.lock.yml line 168
Step action: Runs echo "::error::..." commands to display cross-repo configuration guidance on failure.
Issue:
The step name reads as a noun phrase with no verb. The established pattern for steps that print/echo output uses "Print": compare with "Print firewall logs", "Print prompt". The step emits error annotations, so "Print" accurately describes the action.
Suggested improvement:
"Cross-repo setup guidance" → "Print cross-repo setup guidance"
Source file (compiler-generated): pkg/workflow/compiler_activation_job.go line 185
Agentic Task Description
To fix these step names:
-
"Super-linter" — Edit .github/workflows/super-linter.md, change name: Super-linter to name: Run super-linter, then recompile with gh aw compile super-linter.md.
-
"Cross-repo setup guidance" — Edit pkg/workflow/compiler_activation_job.go line 185, change " - name: Cross-repo setup guidance\n" to " - name: Print cross-repo setup guidance\n", then recompile affected workflows (smoke-workflow-call.md, smoke-workflow-call-with-inputs.md).
Related Files
- Source workflow:
.github/workflows/super-linter.md
- Compiler source:
pkg/workflow/compiler_activation_job.go
- Compiled workflows:
.github/workflows/super-linter.lock.yml, smoke-workflow-call.lock.yml, smoke-workflow-call-with-inputs.lock.yml
- Naming patterns cache:
/tmp/gh-aw/cache-memory/step-name-alignment/patterns.json
Priority
This issue is Medium Priority — consistent naming aids readability and contributor onboarding, and these are straightforward fixes.
AI generated by Step Name Alignment for daily maintenance
Generated by Step Name Alignment · ● 260.2K · ◷
Step Name Alignment Issues
Found in:
.github/workflows/super-linter.lock.yml(line 1290).github/workflows/smoke-workflow-call.lock.yml(line 171).github/workflows/smoke-workflow-call-with-inputs.lock.yml(line 168)Summary
Two step names lack the imperative verb required by the established naming convention. All peer steps in this codebase use an action verb as the first word (e.g., "Run linter", "Print firewall logs"), but these two steps omit the verb entirely.
Issues Identified
1. [Medium Priority] Missing verb: "Super-linter" → "Run super-linter"
Current step name:
super-linter.lock.ymlline 1290:Super-linterStep uses:
super-linter/super-linter@9e863354e3ff62e0727d37183162c4a88873df41Issue:
The step name is just the tool name with no imperative verb. The established pattern requires a verb: compare with "Run unit tests", "Run linter", "Run stale-repos tool", "Run compile with security tools".
Suggested improvement:
"Super-linter"→"Run super-linter"Source file:
.github/workflows/super-linter.mdline 392. [Medium Priority] Missing verb: "Cross-repo setup guidance" → "Print cross-repo setup guidance"
Current step name (compiler-generated):
smoke-workflow-call.lock.ymlline 171smoke-workflow-call-with-inputs.lock.ymlline 168Step action: Runs
echo "::error::..."commands to display cross-repo configuration guidance on failure.Issue:
The step name reads as a noun phrase with no verb. The established pattern for steps that print/echo output uses "Print": compare with "Print firewall logs", "Print prompt". The step emits error annotations, so "Print" accurately describes the action.
Suggested improvement:
"Cross-repo setup guidance"→"Print cross-repo setup guidance"Source file (compiler-generated):
pkg/workflow/compiler_activation_job.goline 185Agentic Task Description
To fix these step names:
"Super-linter" — Edit
.github/workflows/super-linter.md, changename: Super-lintertoname: Run super-linter, then recompile withgh aw compile super-linter.md."Cross-repo setup guidance" — Edit
pkg/workflow/compiler_activation_job.goline 185, change" - name: Cross-repo setup guidance\n"to" - name: Print cross-repo setup guidance\n", then recompile affected workflows (smoke-workflow-call.md,smoke-workflow-call-with-inputs.md).Related Files
.github/workflows/super-linter.mdpkg/workflow/compiler_activation_job.go.github/workflows/super-linter.lock.yml,smoke-workflow-call.lock.yml,smoke-workflow-call-with-inputs.lock.yml/tmp/gh-aw/cache-memory/step-name-alignment/patterns.jsonPriority
This issue is Medium Priority — consistent naming aids readability and contributor onboarding, and these are straightforward fixes.