-
Notifications
You must be signed in to change notification settings - Fork 50
Description
Step Name Alignment Issue
Priority: Medium
Category: Glossary terminology alignment
Summary
Several step names use "cache memory" and "repo memory" (non-hyphenated) when they should use "cache-memory" and "repo-memory" (hyphenated) according to the project glossary.
Issues Identified
Inconsistent Hyphenation: cache memory → cache-memory
Current step names:
- "Append cache memory instructions to prompt"
- "Restore cache memory file share data"
- "Restore cache memory file share data (focus-areas)"
Issue:
The project glossary defines "Cache Memory" with the guidance: "Use hyphenated form in technical contexts" and provides examples like "cache-memory" and "Create cache-memory directory". These step names are in technical contexts but use the non-hyphenated form.
Suggested improvements:
- "Append cache-memory instructions to prompt"
- "Restore cache-memory file share data"
- "Restore cache-memory file share data (focus-areas)"
Glossary reference: See Cache Memory
Inconsistent Hyphenation: repo memory → repo-memory
Current step names:
- "Append repo memory instructions to prompt"
Issue:
Similar to cache-memory, the glossary indicates that "repo-memory" should use the hyphenated form in technical contexts, matching patterns seen in steps like "Clone repo-memory branch", "Download repo-memory artifact", etc.
Suggested improvement:
- "Append repo-memory instructions to prompt"
Glossary reference: See Cache Memory (repo-memory follows the same pattern)
Context
This issue was discovered during the daily step name alignment check on 2026-01-15. The analysis scanned 124 workflows and reviewed 173 unique step names.
Good news: Previous issues identified on 2026-01-14 have been successfully resolved:
- ✅ "Downloading container images" → "Download container images" (imperative form) - FIXED
- ✅ "Set up" vs "Setup" inconsistency - FIXED (all now use "Setup")
Impact
Consistency: Most step names (16+ occurrences) correctly use the hyphenated form. The 4 non-hyphenated instances create inconsistency.
Examples of correct usage in other steps:
- "Create cache-memory directory"
- "Download cache-memory artifact (default)"
- "Save cache-memory to cache (focus-areas)"
- "Clone repo-memory branch (campaigns)"
- "Upload repo-memory artifact (default)"
Agentic Task Description
To fix these step names:
- Locate source workflows - These step names are likely generated by the workflow compiler in shared action templates, not individual workflow
.mdfiles - Update templates - Check these locations for the step name definitions:
actions/*/action.ymlfiles that define reusable actions- Workflow compiler code that generates these standardized steps
- Shell scripts that append instructions to prompts
- Apply hyphenation - Change "cache memory" → "cache-memory" and "repo memory" → "repo-memory" in step name strings
- Recompile workflows - Run
gh aw compileto regenerate all.lock.ymlfiles - Verify consistency - Confirm all instances now use the hyphenated form
Related Files
Likely locations to check:
.github/actions/*/action.yml- Reusable GitHub Actionscompiler/- Workflow compilation code.github/workflows/*.md- Source workflow files (if they explicitly override step names)
Priority Justification
Medium Priority because:
- ✅ Not misleading (meaning is clear)
⚠️ Inconsistent with established glossary and existing patterns⚠️ Only 4 occurrences but affects multiple workflows- ✅ Easy to fix once the source template is located
🤖 AI generated by Step Name Alignment workflow for daily maintenance
AI generated by Step Name Alignment