coder-memory-store

Stage coding insights into a date-bucketed brain2 inbox.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/VinhHung1999/memory-system-plugin --skill coder-memory-store-vinhhung1999
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coder-memory-store
Source: https://github.com/VinhHung1999/memory-system-plugin/tree/main/plugins/memory-system/skills/coder-memory-store
Command: npx skills add https://github.com/VinhHung1999/memory-system-plugin --skill coder-memory-store-vinhhung1999

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stage universal coding insights into Hung's brain2 inbox by automatically staging lessons from difficult tasks to a date-bucketed raw inbox, enabling later review and promotion to a curated wiki.

Core Features & Use Cases

  • Auto-invokes after difficult tasks with broadly-applicable insights (non-obvious bugs, surprising patterns, hard-won fixes) and stores them in the daily inbox.
  • Writes to the staging inbox under ${SECOND_BRAIN_VAULT}/raw/<YYYY-MM-DD>/code-knowledge/<domain>/<bugs|patterns>/<filename>.md as the date bucket.
  • Triggers with --store or when the user expresses frustration; skips trivial or project-specific patterns (built-in auto memory handles those).

Quick Start

Store a coding insight after finishing a difficult task using the --store trigger.

Frequently Asked Questions about coder-memory-store

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically save coding insights and debugging lessons to a knowledge inbox?

Automatically stage coding insights by invoking the tool after difficult tasks to capture non-obvious bugs and hard-won fixes into a date-bucketed raw inbox for later review.

What is the best way to capture cross-project coding patterns for later review?

Capturing cross-project coding patterns is handled by staging broadly applicable insights into a daily brain2 inbox, skipping trivial or project-specific patterns that built-in auto memory already manages.

How do I store non-obvious bugs into a retrievable knowledge feed?

Store non-obvious bugs by writing them to the staging inbox under the vault path as a date bucket, transforming hard-won lessons into a retrievable knowledge feed.

Does the brain2 inbox staging respect the vault permission model?

Yes, staging insights into the brain2 inbox respects the vault permission model while saving universal coding lessons to the raw date-bucketed directory.

When should I not use automated coding lesson staging?

Avoid automated coding lesson staging for trivial or project-specific patterns, as the built-in auto memory handles those. It is designed only for broadly applicable insights after difficult tasks.