omo-senpi

@code-yeongyu/omo-senpi is the Senpi edition of OMO packaged as one Pi package. It loads one generated extension entry from extensions/omo.js and generated skills from skills/.

Shipped skills

The plugin ships 19 skills by default:

• ast-grep — structural code search and rewrites
• coding-agent-sessions — find, read, and reconstruct coding-agent session transcripts
• debugging — hypothesis-driven runtime debugging across languages
• frontend — UI/UX/visual design, styling, layout, and frontend implementation
• git-master — advanced Git operations, history surgery, and workflow automation
• hyperplan — adversarial 5-member cross-critique planning
• init-deep — deep project initialization and scaffold setup
• lsp-setup — Language Server configuration and troubleshooting
• programming — type-strict, modern-stack programming guidance
• refactor — safe refactoring and code quality improvement
• remove-ai-slops — clean AI-generated code smells
• review-work — multi-angle implementation and PR review
• start-work — execute a Prometheus work plan with Boulder state
• ultimate-browsing — escalation browsing for blocked or hard-to-reach pages
• ultrawork — ultrawork mode directive
• ulw-loop — goal-like ultrawork loop
• ulw-plan — adversarial planning workflow
• ulw-research — ultra-wide research orchestration
• visual-qa — visual QA for web and terminal UIs

Install

Build the plugin artifacts before installing:

bun run --cwd packages/omo-senpi build

Then install the built local path:

senpi install /absolute/path/to/omo/packages/omo-senpi/plugin

The OMO installer will also support the Senpi target:

omo install --platform=senpi

Only local-path installs are supported in v1. git: and npm: installs are not supported because extensions/ and skills/ are generated build outputs, not checked-in source trees.

Disable Components

Disable individual OMO Senpi components through the adapter's per-component disable flags after installation. Do not edit files under extensions/ or skills/; those directories are regenerated by the build.

LSP Migration

The Senpi LSP tools are always registered so the harness can show the same six tools in every project: lsp_diagnostics, lsp_goto_definition, lsp_find_references, lsp_symbols, lsp_prepare_rename, and lsp_rename. Runtime execution is handled by the packaged OMO LSP daemon, not by a vendored Senpi client.

Project-local .pi/lsp-client.json command or env entries are ignored for safety. Move custom LSP command definitions to your user .pi/lsp-client.json; project configs may keep safe fields such as extensions, language IDs, and priorities. lsp_rename still runs sequentially, and post-edit diagnostics keep using the daemon after edits without stopping it.