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…
Review reusable project knowledge and decide what belongs in project memory, notepad, or durable docs
$ npx -y skills add Yeachan-Heo/oh-my-claudecode --skill remember --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/rememberContext preview
The summary Claude sees to decide when to auto-load this skill.
Review reusable project knowledge and decide what belongs in project memory, notepad, or durable docs
name: remember description: Review reusable project knowledge and decide what belongs in project memory, notepad, or durable docs
Use this skill when the user wants to preserve or organize useful knowledge discovered during a session.
Promote durable, reusable knowledge into the right memory surface instead of leaving it buried in chat history.
1. Gather the relevant session findings. 2. Classify each item:
3. Propose the best destination for each item. 4. Write or update only the appropriate memory surface. 5. Call out duplicates or conflicts that should be cleaned up.
For Codex users: Check out oh-my-codex — the same orchestration experience for OpenAI Codex CLI. Liked OmC but found it a bit overkill? Try gajae-code.
Repo: Yeachan-Heo/oh-my-claudecode
Writing-time discipline for documents agents consume (the five surfaces, specs, tickets, .omc/skills/) — every rule checkable and carrying a why, steps before…
Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode
Shipyard's navigator — chart a foggy effort (destination unclear, questions not yet stateable) into a map of decision tickets on the repo's issue tracker, then…
Process-first advisor routing for Claude, Codex, Gemini, Antigravity, Grok, or Cursor via `omc ask`, with artifact capture and no raw CLI assembly
Stateful single-mission improvement loop with strict evaluator contract, markdown decision logs, and max-runtime stop behavior