Semantic Bug Detector

Find bugs where the code is syntactically fine and type-correct but does the wrong thing. → static-bug-detector catches provable errors; this skill catches violated intent.

The intent question

You cannot find a semantic bug without a model of intent. For each function, establish intent from (in order of reliability):

1. A failing test (the assertion is the intent)
2. A docstring / type signature / name that makes a contract (sort should sort; retry(n) should try at most n+1 times)
3. An algorithm name (if the function is called binarySearch, you know what invariants it should hold)
4. Surrounding usage (what do callers assume about the return value?)

If you have none of these, you are not detecting bugs — you are generating hypotheses.

Signal catalog — semantic smells that correlate with real bugs