Communitygithub.com

记忆管理

审查可复用的项目知识,并决定哪些应存入项目记忆、记事本或持久化文档。

记忆管理 是什么?

该技能旨在帮助将会话中发现的有用知识持久化到正确的存储位置,避免信息埋没在聊天历史中。它支持多种记忆表面:项目记忆(持久化团队/项目知识)、记事本优先级(下一轮对话的高信号上下文)、记事本工作区(临时活跃会话笔记)以及文档/AGENTS/CLAUDE文件(持久化指令和约定)。工作流程包括收集相关发现、按类型分类(如持久化项目事实、临时工作笔记、操作者偏好或指令、重复/过时/冲突信息)、建议最佳存储位置、更新相应的记忆表面,并标记需清理的重复或冲突项。该技能强调不将所有内容存入同一个存储区,优先将持久化团队知识存入项目记忆,将短命工作上下文存入记事本,并保持条目简洁可操作。

兼容平台✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/Yeachan-Heo/oh-my-claudecode/tree/main/skills/remember

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

记忆管理 是做什么的?

当用户希望保存或组织会话中发现的有用知识时,使用此技能。

目标

将持久的、可复用的知识提升到正确的记忆表面,而不是将其埋在聊天历史中。

记忆表面

  • 项目记忆 — 持久的团队/项目知识
  • 记事本优先级 — 下一轮对话的高信号上下文(简短)
  • 记事本工作区 — 临时活跃会话笔记
  • 文档 / AGENTS / CLAUDE 文件 — 真正适合持久化存储的指令和约定

工作流程

  1. 收集相关的会话发现。
  2. 对每条项目进行分类:
    • 持久的项目事实
    • 临时工作笔记
    • 操作者偏好或指令
    • 重复/过时/冲突信息
  3. 为每条项目建议最佳存储位置。
  4. 仅写入或更新相应的记忆表面。
  5. 标出应清理的重复项或冲突项。

规则

  • 不要将所有内容都转储到一个存储区。
  • 优先将持久团队知识存入项目记忆。
  • 优先将短命工作上下文存入记事本。
  • 保持条目简洁且可操作。
  • 如果某件事不确定,将其标记为不确定,而不是作为事实存储。

输出

  • 存储了什么
  • 存储在哪里
  • 发现的任何重复/冲突项

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

agent-doc-discipline

Writing-time discipline for documents agents consume (the five surfaces, specs, tickets, .omc/skills/) — every rule checkable and carrying a why, steps before reference, one meaning in one home, no restating what the environment already says. Mandatory at drydock seed generation and the launch C5 sediment pass; opt-in for any other agent-facing doc edit. The companion of minimal-code-discipline: that one disciplines code, this one disciplines papers.

ai-slop-cleaner

Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode

ask

Process-first advisor routing for Claude, Codex, Gemini, Antigravity, Grok, or Cursor via `omc ask`, with artifact capture and no raw CLI assembly

ask-navigator

Shipyard

autopilot

Full autonomous execution from idea to working code

autoresearch

Stateful single-mission improvement loop with strict evaluator contract, markdown decision logs, and max-runtime stop behavior

cancel

Cancel any active OMC mode (autopilot, ralph, ultragoal, swarm, ultrapilot, pipeline, team) and clean up retired legacy state

configure-notifications

Configure notification integrations (Telegram, Discord, Slack) via natural language

debug

Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction

deepinit

Deep codebase initialization with hierarchical AGENTS.md documentation

deep-interview

Socratic deep interview with mathematical ambiguity gating before explicit execution approval

drydock

Lay the keel of the shipyard harness in any repo — the 4-pillar shared environment (Context, Rules, Tools, Standards) across 5 surfaces (CLAUDE.md, skills, design-system, mcp/cli, shared context) so that every human and agent inherits the same design language and anyone can ship. Run once per repo; re-run with --check to audit drift.

execute

Carry an approved task through to working, verified code

external-context

Invoke parallel document-specialist agents for external web searches and documentation lookup

graph

Deterministic orchestration graph runtime - declarative DAG pipelines with journal-based crash recovery

harbor

Harbor intake for external work — the captain only handles unresolved decisions. Sweeps incoming issues and PRs, verifies every claim before disposition, reuses every decision already made, and hands the maintainer a docket whose pending items each carry one question with options, recommendation, impact and evidence. Agent-autonomous for facts and for actions covered by standing authorization; signed for every new judgment. Never merges.

hud

Configure HUD display options (layout, presets, display elements)

launch

Shipyard

loft

Loft the shape before cutting steel — answer a design question that prose cannot settle by building a throwaway artifact: a pure logic module in a clickable shell, or structurally different UI variants behind one route. The captain reacts to the artifact; the answer folds into the decision; the artifact never docks. Use when a design question stalls in words, when a navigator map carries a loft ticket, or when a spec discussion reaches

minimal-code-discipline

YAGNI-ladder coding discipline for writing changes — existence-first, reuse before writing, dependency ladder, shortest correct diff, with non-negotiables that must never be minimized away

相关技能