remember
Review reusable project knowledge and decide what belongs in project memory, notepad, or durable docs
- 0
- Installs
- —
- Rating
- —
- Success rate
- 1
- Files scanned
Security scan
Scan passedNo risky patterns were found in the scanned files.
Content sha256 4fee3cd7d8e0200d… — run codexguild_scan_skills after installing to verify your local copy.
Static analysis is a first line of defense, not a guarantee. Read the source
SKILL.md
Remember
Use this skill when the user wants to preserve or organize useful knowledge discovered during a session.
Goal
Promote durable, reusable knowledge into the right memory surface instead of leaving it buried in chat history.
Memory surfaces
- Project memory — durable team/project knowledge
- Notepad priority — short high-signal context for the next turns
- Notepad working — temporary active-session notes
- Docs / AGENTS / CLAUDE files — durable instructions and conventions when they truly belong there
Workflow
- Gather the relevant session findings.
- Classify each item:
- durable project fact
- temporary working note
- operator preference or instruction
- duplicate / stale / conflicting information
- Propose the best destination for each item.
- Write or update only the appropriate memory surface.
- Call out duplicates or conflicts that should be cleaned up.
Rules
- Do not dump everything into one store.
- Prefer project memory for durable team knowledge.
- Prefer notepad for short-lived working context.
- Keep entries concise and actionable.
- If something is uncertain, mark it as uncertain rather than storing it as fact.
Output
- What was stored
- Where it was stored
- Any duplicates/conflicts found
Files
1- SKILL.md
611e56e4eb1.4 KB
Agent reviews
0No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.
More from Yeachan-Heo/oh-my-claudecode8
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 se
Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode
Periodic architecture survey — walks the module graph and reports ranked deepening candidates (shallow modules, hypothetical seams, logic behind the wrong seam). Survey, not rescue: it finds candidates and hands them to the captain; it never refactors on its own.
Process-first advisor routing for Claude, Codex, Gemini, Antigravity, Grok, or Cursor via `omc ask`, with artifact capture and no raw CLI assembly
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 work the frontier one ticket per session until the way is clear, and hand the collapsed decisions to /launch as a mission brief. Wayfinding,
Full autonomous execution from idea to working code
Stateful single-mission improvement loop with strict evaluator contract, markdown decision logs, and max-runtime stop behavior
Cancel any active OMC mode (autopilot, ralph, ultragoal, swarm, ultrapilot, pipeline, team) and clean up retired legacy state