R002 VagueVerbs
- Applies to
- Rules files (CLAUDE.md, AGENTS.md, .mdc, .cursorrules, Copilot instructions, GEMINI.md, .windsurfrules)
- Severity
- Warning (−4 per finding, max −30)
- Summary
- Pattern-based: instructions use verbs with no checkable outcome.
- Flags
- "handle", "manage", "deal with", "ensure", "improve", "optimize", "clean up" opening an instruction, optionally after always / must / should / never / do not. "properly", "appropriate(ly)", "as needed" in an instruction. Instruction lines only (instruction sentence as in R001). Skipped: table rows; inline code, links, paths, file names; a term followed by code, a path, a parenthesized list, "e.g.", three or more listed items, or a colon; "clean up / handle / manage" followed by files, folders, directories, branches, containers, processes, worktrees, temp data, volumes, subscriptions, listeners or timers; a verb followed by a purpose ("to …") or a method ("with / using / via / through …", not "with proper …"); "ensure" after inline code on the line, or followed by a checkable statement or "to avoid / prevent"; a qualifier in an "ensure" clause after inline code, in a verify / check / confirm / test / assert clause, followed by a gerund ("properly functioning") or a purpose or condition ("appropriately for …"), or after more / most / less / least; "as needed" after inline code in the clause; "optimize for"; "where / when / if / as appropriate".
- Measured false-positive rate
- 37% (11 of 30) and 40% (12 of 30), two judges, ruleset v4. Methodology
Before
- Handle errors properly.
After
- Return 400 with a ProblemDetails body when validation fails.
Fix
- Name the concrete action, file, or command.