← all publishers

OmexIT

@omexit source repo

Report this profile Claim this profile

• 11 skills
• 0 followers
• 17 hours ago last updated

1. ▌
   E2e · omexit bundle

   Use when an implementation needs proof against the live running stack: after build completes, before ship, or when asked to verify, e2e-test, smoke-test, or demo that an API, UI, or DB change actually works.
   0 installs
2. ▌
   Plan · omexit

   Use when a feature, refactor, or fix needs an implementation plan before coding - turning an approved spec, ticket, or explicit user request into an executable, verifiable plan document. Also when picking work back up after a context reset or a break: "status?", "what is pending?", "where were we".
   0 installs
3. ▌
   Ship · omexit

   Use when work is ready to leave the machine - committing, opening a PR/MR, merging, promoting branches, or tagging a release ("commit and merge to release-candidate", "promote develop to main", "commit, PR, merge").
   0 installs
4. ▌
   Spec · omexit bundle

   Use when defining or changing WHAT to build - a new feature idea, a PRD to write or update, or scope that needs challenging before implementation starts.
   0 installs
5. ▌
   Audit · omexit bundle

   Use when asked to review work: "review this", "any issues here", "review the PRD against the code", or a review of a diff, module, architecture, or design/spec document - including multi-expert panel reviews ("review with a DDD expert and an asset-finance expert"). Also when running a removal-first simplification sweep: "what can we remove", "product simplification review".
   0 installs
6. ▌
   Debug · omexit

   Use when something is broken and the cause is not yet established: a bare "fix" or "fix this", a pasted stack trace, error payload, or failing log, "X is not working", "investigate why X fails", a failing or flaky test, a crash, hang, regression, incident, or "why is this happening". Applies before any fix is proposed or applied.
   0 installs
7. ▌
   Ledger · omexit bundle

   Use when writing or reviewing code that posts, holds, voids, reverses, or reconciles money movements - double-entry postings, wallet balances, idempotency keys, FX conversion, or Blnk / pgledger integration.
   0 installs
8. ▌
   Temporal · omexit bundle

   Use when writing or changing Temporal workflows or activities in Java - SAGA compensation, retry policies, signals, workflow versioning, replay/determinism issues, or Spring Boot wiring.
   0 installs
9. ▌
   Igaming UI · omexit bundle

   Use for UI work in a sportsbook, betting, or casino (iGaming) product, including design review or visual critique of one: odds displays, betslips, live-event and suspended-market states, game lobbies and grids, and wallet, deposit, and balance surfaces.
   0 installs
10. ▌
    Migrations · omexit bundle

    Use when creating or reviewing database migrations - Liquibase or Flyway, new tables, columns, indexes, constraints, backfills, or any DDL against Postgres.
    0 installs
11. ▌
    Spring API · omexit bundle

    Use when creating or modifying REST endpoints, controllers, DTOs, or error handling in Java Spring services - response envelopes, pagination, Problem Details, package layout.
    0 installs