memory▌

>-

Uses Rekall memory forensics framework to analyze memory dumps for process hollowing, injected code via VAD anomalies, hidden processes, and rootkit detection. Applies plugins like pslist, psscan, vadinfo, malfind, and dlllist to extract forensic artifacts from Windows memory images. Use during incident response memory analysis.

Manages long-lived learnings and recurring patterns that gstack has collected across sessions.

Saves decisions, git state, and pending work so future sessions can resume without reconstructing context from scratch.

Restores saved context, including across branch changes and workspace handoffs.

Weekly engineering retrospective over code activity, trends, and team contributions.

Quality dashboard skill that wraps project checks and reports a weighted health score and trend line.

Keep vector memory lean. Prevent token waste from junk memories.

Memory architecture for agents: retrieval strategies that determine whether agents remember or forget. \n \n Covers five memory types: short-term (context window), long-term (vector stores), working memory, episodic memory, and semantic memory, each suited to different information patterns \n Emphasizes retrieval as the core challenge; provides chunking strategies, embedding quality guidance, and metadata filtering to surface the right memories at decision time \n Includes anti-patterns like sto

Persistent, searchable memory bank for AI agents with automatic project documentation sync. \n \n Provides four core MCP tools: memory_search for querying by text/type/tags, memory_write for recording knowledge and decisions, memory_read for retrieving specific entries, and memory_stats for usage analytics \n Organizes memories by type (architecture, patterns, decisions) and supports custom tagging for flexible retrieval and organization \n Runs as an MCP server that syncs with your project work