🦛 Hippo Memory Insights — 2026-05-08

[github-actions[bot]]

Summary

• Memories in store: 525 (473 episodic, 52 semantic, 0 stale)
• New lessons learned from commits today: 0 (no fix/revert/bug commits in last 7 days)
• Consolidation: 125 episodic merged → 52 semantic; 25 cross-layer duplicates deduped; 7 low-quality flagged
• Highest-confidence memory: mem_05f7e96e10bc — stale .lock.yml workflow files causing CI churn (score=1.00, verified, retrieved 2×)

---

Top Memories Surfaced

1. mem_05f7e96e10bc (verified, score=1.00, retrieved 2×) — Stale workflow .lock.yml files cause CI churn; always run make recompile after editing markdown workflow files.
2. mem_5b74c0634f76 (verified, score=1.00, retrieved 1×) — node: command not found on GPU/self-hosted paths when node runtime is missing; validate runtimes and PATH early.
3. mem_52c8036cdb72 (score=1.00) — validate-yaml CI job scans all YAML for ANSI escape sequences before other jobs run — do not embed raw escape codes in YAML.
4. mem_0238ab5efffb (score=0.95) — CI will fail if make fmt is skipped before opening a PR; unformatted code blocks all other work.
5. mem_9edf9cfd73b3 (score=0.84) — Skipping make fmt has caused 5 CI failures in a single day — always format before committing.
6. mem_b8ccefa844ba (score=1.00) — JavaScript refactoring guide: skills/javascript-refactoring/SKILL.md — split CJS logic into separate files.
7. mem_5822048d553a (score=0.83) — File splitting decision tree: split when >300 lines or when ≥2 distinct domains are present.

---

Suggested Improvements

Error Patterns

• Stale .lock.yml files (mem_05f7e96e10bc): The highest-confidence recurring incident. After any markdown workflow edit, run make recompile. Consider adding a pre-commit hook or CI lint step that detects out-of-sync .lock.yml files automatically.
• Missing node on self-hosted runners (mem_5b74c0634f76): Validate that runtimes.node is declared in workflow YAML and that node is on PATH before any JS tooling is invoked. A startup health-check step in .github/aw/ would catch this early.

Code Quality

• JavaScript file fragmentation: skills/javascript-refactoring/SKILL.md and pkg/workflow/js/ guidance is in memory but may not be enforced. Consider a lint rule or convention check that flags .cjs files exceeding 300 lines.
• Type-safety patterns: The store contains strong guidance on using distinct string types (e.g., JobName vs StepID) to prevent mix-up bugs. Worth a code-review pass on new workflow-parsing code in internal/.
• Validation complexity: scratchpad/validation-refactoring.md documents a step-by-step guide — ensure it stays current as validation logic evolves.

CI Health

• make fmt gate: CI failures from formatting are the most repeated pattern (5 in one day). A mandatory make fmt --check step before any merge (or a pre-push hook) would eliminate this class entirely.
• YAML ANSI escape validation: The validate-yaml job is a good gate but only runs in CI. Add a local make lint-yaml target so agents catch this before pushing.
• make recompile reminder: Workflow lock files drifting out of sync is flagged as a recurring incident. A CI check comparing the committed .lock.yml to a freshly compiled output would make this self-healing.

Quick Wins

1. Add make fmt --check to pre-push hook — eliminates the rejig docs #1 source of CI failures with ~2 min effort.
2. Add make recompile diff check to CI — catches stale .lock.yml automatically; prevents the recurring incident.
3. Local make lint-yaml target — mirrors the validate-yaml CI job so contributors get fast local feedback.
4. Node PATH validation in workflow startup — one shell check (command -v node || exit 1) prevents the self-hosted node: not found class of failures.
5. Prune 7 low-quality memories — run hippo audit and remove stale/low-signal entries to keep recall precision high.

Longer-term Themes

• Formatting discipline: Multiple memories (score ≥ 0.84) converge on the same message — formatting must happen before commit, not after. This suggests the team would benefit from integrated tooling (e.g., editor format-on-save + CI gate) rather than relying on memory/documentation alone.
• Workflow recompilation lifecycle: Two verified incidents relate to workflow files being edited without recompilation. This is a systemic process gap that merits a dedicated improvement (ADR, tooling, or CI enforcement).
• JavaScript modularization: Several memories reference the JS refactoring skill and file-splitting guidelines, suggesting ongoing tension between file size and modular structure in pkg/workflow/js/. A focused refactoring session is warranted.

---

Memory Health

Metric	Count
Total memories	525
Episodic	473
Semantic (consolidated)	52
At risk (<0.2 strength)	0
Low-quality flagged	7
Duplicates removed this run	25
Avg strength	1.00

Low-quality memories to review

Run mcpscripts hippo --args "audit" to get the full list of 7 low-quality memories flagged during the consolidation pass. These are candidates for pruning to keep recall precision high.

---

References: §25541505618

Generated by Daily Hippo Learn · ● 6.7M · ◷

• expires on May 11, 2026, 6:55 AM UTC