luma-web-review-no-floating-promise-no-void

Replaces void-suppressed floating promises with await or consumePromise handling in TypeScript projects.

17|1|Updated Dec 29, 2019
One-click install
npx skills add https://github.com/LumaKernel/dotfiles --skill luma-web-review-no-floating-promise-no-void-lumakernel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: luma-web-review-no-floating-promise-no-void
Source: https://github.com/LumaKernel/dotfiles/tree/main/common/claude/skills/luma-web-review-no-floating-promise-no-void
Command: npx skills add https://github.com/LumaKernel/dotfiles --skill luma-web-review-no-floating-promise-no-void-lumakernel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? The void promise pattern silences the @typescript-eslint/no-floating-promises lint rule without actually handling errors, hiding unhandled rejections and making it impossible to distinguish intentional fire-and-forget calls from forgotten awaits. ## Core Features & Use Cases - ESLint Configuration Update: Sets ignoreVoid: false on @typescript-eslint/no-floating-promises so void suppression is no longer allowed. - Systematic void Replacement: Greps the codebase for void expressions and replaces each with await or a consumePromise helper based on a decision flow. - consumePromise Helper Implementation: Introduces a minimal or Sentry-integrated helper that catches errors and logs or reports them, placed in the project's utils/shared layer. - Use Case: A TypeScript web project has dozens of void someAsyncCall() statements that swallow errors. This Skill audits each one, converts forgotten awaits, and routes intentional fire-and-forget calls through an error-logging helper, then verifies zero lint errors. ## Quick Start Review this TypeScript project, enable ignoreVoid: false for no-floating-promises, and replace every void promise expression with await or a consumePromise helper.

Frequently Asked Questions about luma-web-review-no-floating-promise-no-void

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

FAQPage Schema
When should I use await instead of consumePromise?▼

Use `await` whenever the caller actually depends on the promise completing or its result, which is the most common case. Reserve consumePromise for genuinely intentional fire-and-forget work such as background tasks or test side effects.