🦛 Hippo Memory Insights — 2026-05-25

[github-actions[bot]]

Summary

• Memories in store: 532 (mostly fresh, <7d, high avg strength, diverse topics)
• New lessons learned from commits today: 0 (no fix/revert/bug commits in the last 7 days)
• Newly merged episodic→semantic: 29 patterns consolidated
• Highest-confidence memory: mem_4afaa0965161 — "Recurring incident: stale workflow .lock.yml files cause churn and CI friction; run make recompile after markdown workflow edits." (score=0.976, verified, retrieved 9x)

---

Top Memories Surfaced

1. mem_4afaa0965161 (verified, CI/workflow, score=0.976) — Stale .lock.yml files from markdown workflow edits cause recurring CI churn; always run make recompile after editing workflow markdown files.
2. mem_54c981bfc72e (code quality, score=0.791) — javascript-refactoring skill: guide for refactoring JavaScript into separate .cjs files.
3. mem_98f16a2f627c (validation, score=0.748) — See scratchpad/validation-refactoring.md for step-by-step refactoring guide and examples.
4. mem_bf15fc906323 (CI, score=0.677) — The validate-yaml job in .github/workflows/ci.yml scans all YAML files for ANSI escape sequences before other jobs run.
5. mem_f9f993d957f2 (error-patterns, score=0.672) — Help text should report errors with actionable suggestions.
6. mem_bdc213856476 (CI, score=0.650) — CI WILL FAIL if make fmt is skipped before PR creation — unformatted code causes immediate CI failures blocking all other work.
7. mem_14eae229796b (CI, score=0.576) — This has caused 5 CI failures in a single day — formatting must be verified before every report_progress call.

---

Suggested Improvements

Error Patterns

• Compile errors skipped pre-commit: Multiple memories (score ≥0.48, retrieved 12-14x) confirm teams repeatedly hit compile errors that could be caught early. Fix: enforce make build && make fmt as Checkpoint 1 immediately after the first significant code edit — don't defer until PR creation.
• list_code_scanning_alerts MCP oversized responses: Always include state: open and severity: critical,high filters to avoid token-bloated MCP responses. Relevant file: any workflow prompt invoking code scanning.
• ANSI escape sequences in YAML: The validate-yaml CI job catches ANSI escapes in YAML files. Any tooling that generates or templates YAML should strip escape codes before writing.

Code Quality

• JavaScript refactoring debt: mem_54c981bfc72e (retrieved 5x) and the javascript-refactoring skill point to a recurring need to split large JS files into .cjs modules. Review files >300 lines in src/ for splitting candidates.
• Type safety gaps: mem_1c38df66aa62 (retrieved 12x) — use typed string aliases (e.g. JobName, StepID) to prevent accidental cross-type assignments; currently inconsistently applied.
• File size discipline: mem_dcfce992eff3 — any file >300 lines with 2+ distinct concerns should be split; worth running a quick audit with wc -l across Go and JS source files.
• scratchpad/validation-refactoring.md: Referenced in high-confidence memory (13 retrievals) — ensure the refactoring guide remains up to date and linked from CONTRIBUTING.md or the developer skill.

CI Health

• Stale .lock.yml files (top verified incident, score=0.976): After any markdown workflow edit, make recompile must be run. Consider adding a pre-push hook or CI check that detects stale lock files.
• Formatting causes ~5 CI failures/day (multiple high-confidence memories): Add make fmt --check as a pre-commit hook to catch this before push. Currently relies on developer discipline.
• Full test suite discouraged locally: make test >5 min is rarely needed locally — CI runs it. Teams should run make test-unit locally and let CI handle integration tests.

Quick Wins

1. Add make recompile to the post-workflow-edit checklist in CONTRIBUTING.md or developer skill — directly addresses the rejig docs #1 verified incident.
2. Add make fmt --check pre-push hook — eliminates the recurring "unformatted code" CI failure pattern (5+ failures/day historically).
3. Update scratchpad/validation-refactoring.md to reflect current validation architecture if it has drifted.
4. Add state: open + severity: critical,high guards to any workflow prompt calling list_code_scanning_alerts to prevent oversized MCP responses.
5. Audit JS files >300 lines in the src/ tree and file splitting tickets for the top 3-5 candidates per the javascript-refactoring skill.

Longer-term Themes

• Two-checkpoint validation discipline: Memories around checkpoint-1 and checkpoint-2 are the most-retrieved cluster (12-16x). This pattern is well-documented but inconsistently followed — a linter or CI step enforcing pre-commit validation would institutionalise it.
• Runtime file-copying architecture: mem_859a76794841 (retrieved 9x) notes the architecture uses runtime file copying instead of embedded scripts. This is an implicit constraint that should be documented more prominently to avoid future regressions.
• Ownership model: A merged episodic pattern around Ownership Rules suggests recurring ambiguity about who owns which part of the codebase — worth formalizing in a CODEOWNERS or ownership doc.

---

Memory Health

Memory store statistics

• Total active memories: 532
• Decayed/removed this cycle: 0
• Episodic→semantic merges: 29 new semantic patterns from 79 episodic entries
• Deduped: 29 redundant semantic patterns removed
• Low-quality memories flagged: 7 (run hippo audit for details)
• Global store promotions: 242 high-value memories auto-shared
• New embeddings: 20 (incremental; 532/532 fully indexed)

Low-confidence memories worth reviewing: mem_46a55aef27a0 (strength=0.30), mem_56be26857e9f (strength=0.30), mem_3744e0a82872 (strength=0.30) — all tagged important-using-skills with low strength; likely outdated guidance.

---

References: §26389851202

Generated by 🦛 Daily Hippo Learn · sonnet46 1.2M · ◷

• expires on May 28, 2026, 8:01 AM UTC

[github-actions[bot]]

This discussion has been marked as outdated by Daily Hippo Learn.

A newer discussion is available at Discussion #34895.