mcpField
L
local-build-reminder

local-build-reminder

github.com/yeachan-heoDevelopment40.4k178 installsUpdated 1d ago
Repository

About local-build-reminder

A Claude Code skill for developers working on a local OMC fork. It reminds them to rebuild compiled JavaScript after TypeScript edits and distinguishes files that do or do not need a build.

Key features

  1. 01Detects local OMC development context
  2. 02Reminds after TypeScript edits
  3. 03Lists file types that need builds
  4. 04Suggests automatic rebuild setup

Use cases

  1. 01Applying TypeScript changes in local OMC
  2. 02Checking why an edit has not taken effect
  3. 03Preparing to restart Claude Code after edits

Install

Copy the command and run it in a terminal.

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

After installing, type/local-build-reminderin Claude Code to confirm it loaded.

Details

From the project README

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.

Comments

Markdown supported