Summary
Hippo repeatedly surfaces a workflow-authoring pitfall: list_code_scanning_alerts calls without narrow filters can produce oversized responses and workflow failures. Memory: mem_0324334270d0.
Rationale
This is one of the clearest actionable workflow-quality lessons in the memory store. The recommended safe pattern is to always include state: open and severity: critical,high, especially in .github/workflows/ prompt content where large tool outputs are expensive and failure-prone.
Next steps
- Search workflow markdown under
.github/workflows/ for list_code_scanning_alerts usage.
- For each occurrence, ensure the prompt explicitly constrains
state: open and severity: critical,high unless a documented exception is required.
- Update any affected workflow docs/examples so the constrained pattern is the default.
- Recompile changed workflow markdown with
make recompile.
Memory: mem_0324334270d0
Generated by 🦛 Daily Hippo Learn · gpt54 · 21.6 AIC · ⌖ 9.63 AIC · ⊞ 5.5K · ◷
Summary
Hippo repeatedly surfaces a workflow-authoring pitfall:
list_code_scanning_alertscalls without narrow filters can produce oversized responses and workflow failures. Memory:mem_0324334270d0.Rationale
This is one of the clearest actionable workflow-quality lessons in the memory store. The recommended safe pattern is to always include
state: openandseverity: critical,high, especially in.github/workflows/prompt content where large tool outputs are expensive and failure-prone.Next steps
.github/workflows/forlist_code_scanning_alertsusage.state: openandseverity: critical,highunless a documented exception is required.make recompile.Memory:
mem_0324334270d0