MCPInstall

local-build-reminder

Remind the user to rebuild OMC after editing TypeScript when running from a local fork. Triggered automatically by the AI whenever it notices it (or the user) just changed a src//.ts file in an OMC dev install.

Installs
178
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/yeachan-heo/oh-my-claudecode --skill local-build-reminder
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads local-build-reminder automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Local Build Reminder

Always-on reminder for OMC fork development. When OMC is running in local mode (HUD shows [OMC#X.Y.ZL] with an L suffix), Claude Code loads compiled JavaScript from dist/ — NOT TypeScript source from src/. Edits to .ts files are invisible to the running plugin until npm run build regenerates dist/.

When to invoke this skill

The AI should mention this reminder whenever any of these happens:

  1. The user (or the AI itself) just edited src/**/*.ts in this repo.
  2. The user asks "why isn't my change working?" / "I edited X but it does the same" after a TS edit.
  3. The user is about to restart Claude Code and the working tree has TS edits with no rebuild.
  4. The user runs an OMC command and expects new behavior tied to a TS edit.

What to say

Surface one clear sentence followed by the exact command. Don't repeat the reminder on every turn — once per "round" of TS editing is enough. Example:

Heads up: you edited src/.... Run npm run build before restarting Claude Code — dist/ won't reflect the change otherwise.

If multiple TS files were edited in a row, just remind once at the end.

When NOT to remind

  • The user only edited .mjs / .cjs / .md / .json — those load directly from disk, no build needed.
  • The user is in a Claude Code session that isn't running OMC locally (no L in the HUD).
  • A tsc --watch / npm run dev:full is already running in the background — those rebuild automatically on save.
  • The user just asked an unrelated question; don't shoehorn the reminder into off-topic responses.

File-type cheat sheet

PathRestart picks up edit?Needs build?
src/**/*.tsOnly after buildYes
templates/hooks/**/*.mjsYesNo
scripts/**/*.mjs / *.cjsYesNo
skills/**/SKILL.mdYesNo
agents/**/*.mdYesNo
commands/**/*.mdYesNo
.claude-plugin/plugin.jsonYes (on Claude restart)No
docs/**/*.mdCosmetic onlyNo

One-command setup for hands-free dev

If the user is iterating heavily and tired of remembering the build, suggest:

npm run dev:full

This runs tsc --watch plus all bridge builders in parallel — every save triggers a rebuild within a second, so restart Claude Code is all that's needed afterwards.

Detection signal — how the AI knows it's "local mode"

The HUD's [OMC#X.Y.ZL] suffix is the visible cue. Programmatically, the detection lives in src/lib/version.ts::isRuntimePackageLocal() and triggers on any of: .git/ at package root, src/ at package root, package reached via symlink/junction, or any ancestor is a symlink/junction.

When running inside the OMC fork repo itself, the AI is by definition in local mode — the reminder always applies.

FAQ

What does the local-build-reminder skill do?

Remind the user to rebuild OMC after editing TypeScript when running from a local fork. Triggered automatically by the AI whenever it notices it (or the user) just changed a src//.ts file in an OMC dev install.

How do I install local-build-reminder?

Run npx skills add https://github.com/yeachan-heo/oh-my-claudecode --skill local-build-reminder in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/local-build-reminder/ (personal) or .claude/skills/local-build-reminder/ (project).

Which AI agents can use local-build-reminder?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is local-build-reminder safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains local-build-reminder?

It is published by yeachan-heo in yeachan-heo/oh-my-claudecode. It has 178 recorded installs.

More from yeachan-heo/oh-my-claudecode

View all →

ai-slop-cleaner

yeachan-heo/oh-my-claudecode

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

Testing & QA1.6K installs

ralplan

yeachan-heo/oh-my-claudecode

Consensus planning entrypoint that auto-gates vague ralph/autopilot/team requests before execution

hud

yeachan-heo/oh-my-claudecode

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

Frontend & Design1.1K installs

deepinit

yeachan-heo/oh-my-claudecode

Deep codebase initialization with hierarchical AGENTS.md documentation

autopilot

yeachan-heo/oh-my-claudecode

Full autonomous execution from idea to working code

1K installs

deep-interview

yeachan-heo/oh-my-claudecode

Socratic deep interview with mathematical ambiguity gating before explicit execution approval

1K installs

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.