remember
starsforks
How to install remember?
jmstar85/oh-my-githubcopilot/remember
$npx -y skills add jmstar85/oh-my-githubcopilot --skill rememberPromote reusable project knowledge to the right memory surface. Activate when user says: remember this, save this, store this, remember, memorize, keep this for later.
SKILL.md
| 1 | # Remember |
| 2 | |
| 3 | Promote durable, reusable knowledge into the right memory surface instead of leaving it buried in chat history. |
| 4 | |
| 5 | ## When to Use |
| 6 | - User wants to preserve knowledge discovered during a session |
| 7 | - Organizing scattered findings into structured memory |
| 8 | - Cleaning up duplicate or conflicting stored information |
| 9 | |
| 10 | ## When NOT to Use |
| 11 | - Ephemeral task notes → just keep in conversation |
| 12 | - Already documented in code or docs → reference directly |
| 13 | |
| 14 | ## Memory Surfaces |
| 15 | |
| 16 | | Surface | Use For | Durability | |
| 17 | |---------|---------|------------| |
| 18 | | **Project memory** | Durable team/project knowledge | Permanent | |
| 19 | | **Session context** | Short-lived working notes | Session only | |
| 20 | | **Docs / Instructions** | Conventions, instructions | Permanent | |
| 21 | |
| 22 | ## Workflow |
| 23 | |
| 24 | 1. Gather the relevant session findings |
| 25 | 2. Classify each item: |
| 26 | - Durable project fact |
| 27 | - Temporary working note |
| 28 | - Operator preference or instruction |
| 29 | - Duplicate / stale / conflicting information |
| 30 | 3. Propose the best destination for each item |
| 31 | 4. Write or update only the appropriate memory surface |
| 32 | 5. Call out duplicates or conflicts that should be cleaned up |
| 33 | |
| 34 | ## Rules |
| 35 | |
| 36 | - Do not dump everything into one store |
| 37 | - Prefer project memory for durable team knowledge |
| 38 | - Keep entries concise and actionable |
| 39 | - If something is uncertain, mark it as uncertain rather than storing it as fact |
| 40 | |
| 41 | ## Output |
| 42 | |
| 43 | - What was stored |
| 44 | - Where it was stored |
| 45 | - Any duplicates/conflicts found |
| 46 | |
| 47 | --- |
| 48 | |
| 49 | ## Quality Gate (Before Storing) |
| 50 | |
| 51 | Before committing anything to memory, apply this 3-question filter. Skip storage if the answer to any question is "No": |
| 52 | |
| 53 | | Question | Rationale | |
| 54 | |----------|-----------| |
| 55 | | **Is it actionable?** "Does this tell someone what to DO in a future situation?" | Observations are not memory entries; decisions are. | |
| 56 | | **Is it durable?** "Will this still be true in 3 months, or is it tied to a temporary workaround?" | Ephemeral findings belong in session notes, not project memory. | |
| 57 | | **Is it unique?** "Does something close already exist in memory that covers this?" | Duplicate entries create confusion; prefer updating existing entries. | |
| 58 | |
| 59 | ### Examples |
| 60 | |
| 61 | | Item | Actionable? | Durable? | Unique? | Store? | |
| 62 | |------|-------------|----------|---------|--------| |
| 63 | | "Use `bcrypt` cost=12 for passwords in this project" | ✅ | ✅ | ✅ | **YES** | |
| 64 | | "API was slow today because server was rebooting" | ❌ | ❌ | ✅ | **NO** — ephemeral | |
| 65 | | "Always run `npm run build` before pushing" | ✅ | ✅ | Check existing | **YES if not already stored** | |
| 66 | | "The login page has a bug in dark mode" | ❌ | ❌ | ✅ | **NO** — file a bug, not a memory entry | |
| 67 | | "We prefer `interface` over `type` for object shapes" | ✅ | ✅ | Check existing | **YES if not in coding-standards** | |
| 68 | |
| 69 | ### When to Update vs Create |
| 70 | |
| 71 | - **UPDATE** an existing entry if the new information refines, corrects, or supersedes it |
| 72 | - **CREATE** a new entry only if no existing entry covers the topic |
| 73 | - **DELETE** entries that are provably outdated (check with user first) |
| 74 | |
| 75 | ## See Also |
| 76 | |
| 77 | - `/coding-standards` — canonical rules reference (no need to duplicate into memory) |
| 78 | - `/skill-stocktake` — audit memory surfaces for quality |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
