π¦ Hippo Memory Insights β 2026-06-12 #38806
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by Daily Hippo Learn. A newer discussion is available at Discussion #39338. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
mem_4afaa0965161β Stale.lock.ymlfiles cause CI friction; runmake recompileafter markdown workflow edits (verified incident, 36x retrieved, strength 1.00)Top Memories Surfaced
mem_cab727bbe2e5β gh-aw identity:gh awcompiles markdown workflows into GitHub Actions; it is NOT the GitHub Copilot CLI. Keep these separate in documentation and error messages.mem_0324334270d0β MCP safety: Always guardlist_code_scanning_alertscalls withstate: openandseverity: critical,highto avoid oversized MCP responses.mem_3c0154ff3f2dβ Post-merge discipline: Runmake build && make recompileafter merging main to rebuild the binary and recompile all workflow lock files.mem_2704ae961669β Checkpoint 1:make build && make fmtimmediately after the first substantial code change β surfaces compile errors before spending more context on subsequent edits.mem_4afaa0965161(incident, verified) β Stale.lock.ymlfiles are the rejig docsΒ #1 recurring CI friction source;make recompilemust follow every markdown workflow edit.mem_e02072c9ae07(incident, verified) βnode: command not foundon GPU/self-hosted runner paths; validate runtimes andPATHearly.mem_512f4cbb0103β ANSI stripping: The workflow compiler (pkg/workflow/compiler_yaml.go) automatically strips ANSI codes viastringutil.StripANSI()from descriptions, sources, and comments β no manual stripping needed.Suggested Improvements
Error Patterns
.lock.ymlfiles (recurring, verified): This is the most-retrieved incident. Consider adding a pre-commit hook or CI gate that verifies lock files are up-to-date after any.mdworkflow change. The memory has been retrieved 36 times, signalling repeated exposure.list_code_scanning_alertswithout filters consistently causes oversized responses. Add a linter rule or prompt guard to always injectstate: open+severity: critical,high.make fmt. Enforce Checkpoint 1 validation in agent prompts.mem_b3de87b76481, decaying): Verify auth/mode/token setup before triggering reruns on GPU/self-hosted environments. This memory is nearly dead (strength 0.01) β the issue may be resolved or forgotten.Code Quality
validation-refactoring.mdscratchpad and associated memories show a pattern of oversized files. Files >300 lines or spanning 2+ distinct domains should be split. Theskills/javascript-refactoring/SKILL.mdguide is the canonical reference.JobNamevsStepID) prevents accidental mixing β 50x retrieved, suggesting agents frequently benefit from this reminder. Consider codifying more of these patterns inAGENTS.md.code-organizationtag).CI Health
make testis slow (>5 min): Agents should rely on CI for the full test suite. Onlymake test-unit(~3 min) is appropriate during development.validate-yamlANSI scan runs as a pre-gate in CI β any ANSI leak in YAML files will block all other jobs. The compiler strips these automatically for workflow files, but hand-edited YAML still needs care.Quick Wins
make recompileto a post-merge checklist or Makefile alias β resolves the rejig docsΒ #1 CI friction source (stale.lock.yml) with near-zero effort.mem_0324334270d0(guardlist_code_scanning_alerts) β it is retrieved 62x but unpinned; pinning prevents accidental decay.mem_b3de87b76481(Codex auth failures, strength 0.01) β this memory is nearly dead and never retrieved since creation; safe to remove.make build && make fmt(Checkpoint 1) must be run before any additional edits β 52x retrieved but not yet a pinned rule.hippo auditto address the 7 low-quality memories flagged during consolidation.Longer-term Themes
checkpoint-2tag β many are near-duplicates of "run make agent-report-progress and verify zero lint errors before every PR." A targeted consolidation pass on this cluster would reduce recall noise.important-using-skillstag (12 memories) consistently surfaces the BE LAZY principle. Consider elevating this to a pinned rule to reduce redundant skill-loading in agent sessions.Memory Health
Low-strength incidents worth pruning
mem_b3de87b76481β Codex auth failures (strength 0.01, never retrieved since creation 23 days ago). Safe to delete.Consolidation details from this run
hippo auditto review)References:
Beta Was this translation helpful? Give feedback.
All reactions