# Rule explorer Find the code from your report, understand what triggered it, and see a tested repair. Each rule page includes a before-and-after example. [Search by code or topic](/docs/search) · [How to read a finding](/docs/quickstart#2-read-a-finding). ## Instruction and configuration checks
H1Tool Description Ambiguity →Give agents enough information to choose the right tool or skill. H1 covers missing descriptions, vague selection text, naming collisions, overlap, and skill metadata.H2Missing Constraint Scaffolding →An instruction asks for repeated effort without a usable stopping condition or retry budget.H3Schema-Intent Mismatch →The schema and selection contract disagree or leave inputs underspecified.H4Context Boundary Erosion →The instruction asks for unscoped context retention or leaves a detectable context boundary unclear.H5Implicit Instruction Failure →A vague qualifier or implicit instruction leaves the expected behavior unclear.H6Template Format Contract Violation →The output contract gives competing instructions or lacks selected format/version signals.H7Role Confusion →The message sequence contains a selected role or ordering inconsistency.
## Tool descriptions and skill metadata
H1.1Missing description →A selectable tool or skill has no description. Callers cannot learn its purpose from selection-time text.H1.2Underspecified short description →A very short description leaves the action or domain unclear.H1.3Vague opening verb →A short description starts with a broad verb without saying what the tool actually does.H1.4Duplicate tool name →Two tools have the same selection name. A caller cannot address them unambiguously.H1.5Near-duplicate descriptions →Two tools have near-duplicate descriptions, obscuring when to choose each one.H1.6Missing tool differentia →Different wording can still describe the same operation. Neither description gives the caller a useful selection distinction.H1.7Oversized skill description →A skill description exceeds the released 1024-character check. Selection text contains detail better placed in the body.H1.8Missing skill trigger →The description says what the skill contains but gives no recognized situation for selecting it.H1.9Invalid or mismatched skill name →The skill name is invalid or does not match its containing directory.
## File references and Python
H4.5Referenced project file is missing →An instruction sends the agent to a project file that does not exist.P1Uncalibrated Threshold →A threshold-like numeric assignment lacks a nearby recognized calibration or justification comment.P2Embedded Scaffold →A long prompt is embedded directly in Python source. It may be easier to maintain as a concise instruction or a separately versioned file.
## Use rules in your workflow Select families with `--patterns H1 H3`, or choose a [severity threshold](/docs/outputs#set-a-ci-threshold) for CI. Individual H1 subcodes belong to the H1 family. [Automatic fixes](/docs/fixes) describes the supported rewrite. [Instruction preflight](/docs/preflight) is a separate command with its own checks. The [full reference](/docs/reference#structural-detectors-h1-h7) documents the complete detection contracts.