be-integrate-review

Audits outbound vendor HTTP integration code for timeout, retry, and circuit-breaker hazards.

1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/ohmyhotelco/hare-cc-plugins --skill be-integrate-review-ohmyhotelco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: be-integrate-review
Source: https://github.com/ohmyhotelco/hare-cc-plugins/tree/main/backend-webflux-plugin/skills/be-integrate-review
Command: npx skills add https://github.com/ohmyhotelco/hare-cc-plugins --skill be-integrate-review-ohmyhotelco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Outbound calls to third-party vendor APIs fail in ways that never appear in normal tests: ambiguous timeouts, blind retries on non-idempotent bookings, shared circuit breakers, and state drift between your service and the vendor. This Skill audits the {domain}/client/ package to surface those failure modes before they cause duplicate charges or inconsistent state in production. ## Core Features & Use Cases - Critical hazard detection: Flags blind retries on non-idempotent calls, ambiguous timeouts resolved without vendor reconciliation, and cancel flows that write local state before vendor confirmation. - Resilience pattern review: Checks for missing .timeout() on reactive chains, retries without backoff/jitter/caps, retry filters that don't exclude 4xx, circuit breakers shared across vendors, and unbounded fan-out. - Confidence-calibrated reporting: Distinguishes mechanical findings from judgment-based ones, appending needs manual confirmation markers where the source alone cannot prove the issue. - Use Case: After building a hotel booking integration with a supplier API, run this audit on the booking/client/ package to catch a book() call that retries without an idempotency key — a bug that would double-charge customers under vendor instability. ## Quick Start Ask the assistant to run the vendor integration audit on your client package, for example: audit src/main/java/com/example/booking/client for timeout, retry, and circuit-breaker issues.

Frequently Asked Questions about be-integrate-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit vendor API integration code for retry and timeout issues?▼

Run this audit against your domain's client package. It scans WebClient reactive chains for missing .timeout() calls, retries without backoff or idempotency keys, and ambiguous timeout handling that skips vendor reconciliation, then reports findings with fix suggestions.

What is an ambiguous timeout in a vendor API call?▼

An ambiguous timeout occurs when a write call like book() times out and you cannot tell whether the vendor processed it. The correct pattern is to call the vendor's retrieve endpoint to confirm the actual state before marking the operation failed.

Should each vendor have its own circuit breaker?▼

Yes. Sharing one CircuitBreaker instance across multiple vendors means one vendor's failures open the breaker for all of them. The audit flags any CircuitBreakerRegistry name reused across different vendor clients.

When should I not use this vendor integration audit?▼

Skip it for CRUD-only domains with no client package that only call their own database. Use a data-layer audit for DB and query issues, and a security-focused review for PII and log-masking depth instead.

Why is retrying a non-idempotent booking call dangerous?▼

Retrying a create or booking call without an idempotency key can cause the vendor to process the request multiple times, producing duplicate bookings or charges. The audit flags any retried write call that does not pass an idempotency key to the vendor.