A try/catch whose catch only rethrows the same error. It adds nesting and implies handling that does not exist.
Each example shows the exact code shape the rule is looking for, then the smallest version that keeps the intent without hiding risk or adding noise.
export async function loadProfile(userId: string) {
try {
return await api.get(`/users/${userId}/profile`)
} catch (error) {
throw error
}
}Deterministic AST match on JS/TS: flags try statements without `finally` whose catch body is a single `throw err` or `return Promise.reject(err)` of the caught binding.
export async function loadProfile(userId: string) {
return api.get(`/users/${userId}/profile`)
}Remove the try/catch and let the error propagate, or add the context, cleanup, or recovery that would justify it.
Agents wrap calls in try/catch defensively, then have nothing to do in the catch, so they rethrow the error unchanged.
ai-slop/redundant-try-catch
ai-slop
Deterministic AST match on JS/TS: flags try statements without `finally` whose catch body is a single `throw err` or `return Promise.reject(err)` of the caught binding.
Catches that add context (`throw new Error('...', { cause: err })`), log, clean up, or recover, and any try with a `finally` block, are not flagged.
Part of aislop's defensive-pattern detectors for JavaScript and TypeScript, scored in the maintainability tier.