backend-webflux-plugin

Plugin backend-webflux-plugin from marketplace ohmyhotelco in ohmyhotelco/hare-cc-plugins. Commands read from the repo's manifest — 8 days ago.

Skills (20)

• be-api-review

  Audit REST API contracts for HTTP semantics, versioning, and consistency across RouterFunction and annotated web layers.

• be-build

  Run the project build, auto-diagnose failures (compilation, test, checkstyle, dependency, configuration), and apply targeted fixes with up to 3 retries. Trigger on: \"build failing\", \"fix compile errors\", \"auto-fix build\", \"build broken\", \"gradle build failed\" — and Vietnamese/Korean equiva

• be-clean-code

  Audit Java source for DRY, KISS, YAGNI, naming, and structure violations (god classes, deep nesting, long parameter lists). Use when the user asks to check code smells, DRY/KISS/YAGNI, or 'is this file too complex' — distinct from be-review (multi-dimension review orchestration), be-test-review (tes

• be-code

  TDD-implement a CQRS/WebFlux feature: RED-GREEN cycle through command executors, query processors, and router/handler code. Consumes a be-crud scaffold, plan.json, or an existing work document with test scenarios; drafts scenarios manually if none exist. Use be-crud first when no scaffold exists yet

• be-commit

  Create a commit from staged changes with validated message.

• be-crud

  Generate CRUD scaffold for an entity using CQRS layered architecture (R2DBC or MyBatis, functional or annotated web layer).

• be-data

  Audit R2DBC and MyBatis data-layer patterns, schema design, migration safety, and reactive-blocking hazards.

• be-debug

  Systematic debugging with 4-phase methodology: reproduce, hypothesize, test, confirm.

• be-fix

  Read review report and apply TDD-disciplined fixes. Closes the review-fix loop.

• be-init

  Initialize Backend WebFlux Plugin configuration for the current project.

• be-integrate-review

  Audit outbound vendor/HTTP integration code in a {domain}/client/ package for timeout, retry, circuit-breaker, and reconciliation hazards — not for DB/query issues (use be-data) or general PII/log-masking depth (use be-security).

• be-jira-auto

  Jira-to-commit orchestrator that implements a ticket's own stated Technical Approach directly when present, or drafts a Proposed Solution and stops for user confirmation when not, classifies the ticket into a tier (easy/normal/extreme) to scale the review gate, and drives the full be-crud -> be-code

• be-logging

  Audit Java logging patterns for SLF4J usage, structured logging, and security-sensitive log content (secrets, PII, MDC/Reactor context loss across scheduler hops). Use when checking whether log statements are safe, well-formed, and keep correlation IDs intact across Reactor's thread-hopping executio

• be-plan

  Analyze a finalized/reviewing planning-plugin functional spec for {feature} and produce a structured backend implementation plan (plan.json) that be-crud scaffolds from. Use when a planning-plugin spec exists and you need entity/command/query/endpoint mapping before scaffolding. If no spec exists fo

• be-progress

  Show implementation status of work document features: pipeline stage, scenario counts, verify/review/fix history, and the suggested next command. Trigger on: \"progress\", \"pipeline status\", \"show progress\", \"what's the status of {feature}\", \"be-progress\" — and Vietnamese/Korean equivalents:

• be-recall

  Recall development rules and check for violations.

• be-review

  Review a backend feature's code through the code-reviewer agent (6 dimensions + optional spec compliance) and produce a structured report. Use when asked to review a feature or its code.

• be-security

  Audit security vulnerabilities: authentication, authorization, input validation, PII exposure, injection (including MyBatis ${} substitution), and secrets.

• be-test-review

  Standalone audit of existing test code: naming, StepVerifier assertion correctness, coverage gaps, and optional timing gates. Use this to review test quality on demand, independent of the pipeline. Different from be-verify (runs the test suite and gates PASS/FAIL before review) and be-code (writes t

• be-verify

  Read-only verification gate: runs build, checkstyle, tests, and JaCoco coverage and reports structured PASS/FAIL per step — never fixes anything. Use this before be-review to confirm a feature is ready for code review; use be-build instead when you want auto-fix applied. Supports English, Korean, an

Subagents (6)

• backend-planner

  Spec analysis agent that reads functional specifications and produces a structured backend implementation plan (plan.json)

• build-doctor

  Gradle build execution, failure diagnosis, and automatic fix with retry

• code-reviewer

  Multi-dimension code review combining API, data layer (R2DBC/MyBatis), clean code, logging, test quality, architecture, and optional spec compliance checks

• debugger

  Systematic debugger using 4-phase methodology (reproduce, hypothesize, test, confirm)

• implement

  TDD-based feature implementation from work documents or scenario lists

• review-fixer

  TDD-disciplined fixer that reads review reports and applies targeted fixes with appropriate methodology

Hooks (2)

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}/scripts/session-init.sh"

• PostToolUse

  "${CLAUDE_PLUGIN_ROOT}/scripts/validate-build-state.sh"

Similar plugins