ohmyhotelco
Official@ohmyhotelco
ohmyhotelco provides gated migration and code-quality skills for Angular-to-React rewrites, Spring WebFlux backends, and spec-driven frontend delivery.
Agent Skills by ohmyhotelco
Showing 70 vetted skills indexed across 1 GitHub repositories.
fm-test-review
Audits generated Vitest and Playwright migration tests for quality, coverage, and anti-patterns.
fm-plan
Generates a migration-plan.json from page analysis and style-spec for legacy-to-React migration.
fm-gen
Generates a React Router v7 page from a migration plan via a phased TDD pipeline.
fm-route
Manages Strangler Fig route flips for migrated pages at nginx or CloudFront edge layers.
fm-init
Detects legacy Angular apps and monorepo layout to write the frontend migration plugin configuration.
fm-clean-code
Audits generated React migration code for quality, accessibility, and convention compliance.
fm-delta
Re-migrates only changed legacy Angular surface via delta plans while preserving accumulated fixes.
fm-fix
Repairs failed migration gates by auto-detecting fix mode and re-running verification.
fm-audit-codex
Runs an independent Codex audit of migrated page artifacts as an advisory second opinion.
fm-progress
Renders a read-only migration progress dashboard from tracker.json with per-page gate status and next-step guidance.
fm-parity
Runs visual, API contract, WebView bridge, and telemetry parity gates on migrated pages before route flip.
fm-extract
Extracts shared logic from legacy Angular apps into framework-agnostic packages with tests.
fm-secret-audit
Audits legacy environment.ts files to inventory secrets and classify client versus server exposure.
fm-analyze
Analyzes a legacy Angular target and records dependency graphs, shared-package candidates, and required migration gates.
fm-verify
Runs build, TypeScript, Vitest, and ESLint gates on a migrated page and records verified status.
fm-style-spec
Extracts a legacy page's computed styles, assets, and markup structure into style-spec.json via Playwright probing.
fm-e2e
Runs Playwright E2E gate tests on migrated pages with legacy dual-run parity checks.
fm-cascade
Diffs legacy and migrated stylesheets node by node to detect computed-style divergences on real page markup.
be-api-review
Audits Spring WebFlux REST API contracts for HTTP semantics, versioning, and web-layer consistency.
be-build
Diagnoses and fixes Gradle build failures with up to three automated retry attempts.
be-debug
Diagnoses and fixes backend errors using a bounded 4-phase hypothesis-testing methodology.
be-integrate-review
Audits outbound vendor HTTP integration code for timeout, retry, and circuit-breaker hazards.
be-data
Audits R2DBC and MyBatis data-layer code for blocking calls, transaction, schema, and migration issues.
be-crud
Generates CQRS CRUD scaffolds for Spring WebFlux entities with R2DBC or MyBatis persistence.
Frequently Asked Questions About ohmyhotelco
FAQPage SchemaWhat tasks can I automate using ohmyhotelco's skills?▼
You can run end-to-end Angular-to-React page migrations with Strangler Fig route flips, scaffold and TDD-implement Spring WebFlux CQRS features, audit code for security, logging, data-layer, and clean-code issues, and drive specs into wireframes, prototypes, and Astro homepages.
Who are these skills designed for?▼
Frontend engineers migrating legacy Angular monorepos to React, backend engineers building reactive Java services with R2DBC, MyBatis, or JPA, and product teams producing multilingual functional specifications and UI prototypes before implementation.
How do I install and run these skills in practice?▼
Each plugin family starts with an init skill (fm-init, be-init, fe-init, pp-init, hp-init) that detects project layout and writes configuration. Skills are then invoked by name with argument hints, and progress skills report pipeline state and the suggested next step.
What prerequisites and dependencies do the skills require?▼
Migration skills expect legacy Angular apps and a monorepo layout; verification gates require TypeScript, Vitest, ESLint, and Playwright. Backend skills target Java WebFlux projects with Gradle, and design sync optionally uses Stitch, Notion, or Figma MCP connections.
How do the quality gates and review loops work?▼
Read-only verify skills run build, tests, coverage, and lint as PASS/FAIL gates, while review skills produce structured reports across security, test quality, and clean-code dimensions. Fix skills then apply TDD-disciplined repairs and re-run the failed gate until it passes.