メニュー
Use when finishing InboxBridge work, validating a change, preparing a PR, or summarizing the current worktree for handoff. Focuses on the repository's required validation path, Docker readiness, and commit-message expectations.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the user explicitly wants unusually strong pushback, tougher assumption-testing, devil's-advocate reasoning, or a higher-than-normal skepticism setting beyond the repository's baseline directness. Prioritize finding weak logic, missing evidence, bad tradeoffs, and blind spots before endorsing anything.
Use when designing, reviewing, or extending InboxBridge browser extensions for Chromium, Firefox, or Safari. Captures official browser-extension best practices around permissions, storage, auth, packaging, and testing.
Use when changing the React admin UI, the /remote surface, translated copy, layout behavior, or frontend controller/component structure in InboxBridge. Focuses on frontend conventions, translation expectations, and frontend validation.
Use when changing the Quarkus backend, Flyway schema, mailbox import logic, auth/session services, or REST endpoints in InboxBridge. Focuses on backend architecture, transactional boundaries, security invariants, and backend validation.
Use when reviewing, refactoring, or extending the Quarkus backend architecture in InboxBridge. Captures modern Quarkus, Java 25, Maven, testing, package-structure, and backend-boundary best practices adapted to this repository.
Use when reorganizing or extending React code in InboxBridge. Captures the repo's preferred React structure, state, composition, and styling conventions.
| name | inboxbridge-validation-release |
| description | Use when finishing InboxBridge work, validating a change, preparing a PR, or summarizing the current worktree for handoff. Focuses on the repository's required validation path, Docker readiness, and commit-message expectations. |
Use this skill near the end of a task or when asked for release, PR, review, or handoff help.
mvn -q test or a narrower -Dtest=... pass before the full suite when appropriate.cd admin-ui && npm run test:run and cd admin-ui && npm run build.PillboxInput, App live-event, or other frontend regression work, run the narrow Vitest target first, then the full cd admin-ui && npm run test:run before handoff.node site/test-config-generator.mjs to catch locale/catalog drift and public-site markup regressions.docker compose up --build -d unless the user explicitly asked not to or the environment blocks it.https://localhost:3000 and https://localhost:3000/remote.The proposed commit message must include:
CONTRIBUTING.mdCONTEXT.mdAGENTS.mdsite/test-config-generator.mjs