ai-slop/todo-stub manual fix

Orphan TODO stub.

A `// TODO` without an owner, ticket, or completion plan. The kind that survives years.

Bad — what an agent ships

// TODO: handle the retry case
return result

Good — what aislop hands back

// TODO(#1234): retry on 503 with exponential backoff — currently fail-fast
return result

// or just finish it now:
return retry(() => fetch(url), { retries: 3, backoff: 'exp' })

Why an AI agent produces this

Agents punt hard cases under a comment and move on. Ungated TODOs accumulate forever; nobody knows whether they're still relevant or already irrelevant.

Provenance

How this rule is justified.

Rule id

ai-slop/todo-stub

Enforcing engine

ai-slop

Detector strategy

Deterministic regex match: flags TODO/FIXME comments with no owner, ticket reference, or completion plan.

Legitimate code that is NOT flagged

A TODO that carries an owner or ticket reference (e.g. `TODO(#1234)`) is not flagged.

Evidence

Provenance: repeated across public scans as accumulated, ungated deferrals.

← All patterns Scan your repo for this →