agent left debug print statements committed in the model sql

TL;DR

Leftover debug in models usually means Jinja log() prints, temporary select probes, or commented-but-live debug CTEs that change output or spam logs. Remove the debug statements from model SQL (keep useful logging only in macros, behind execute checks), recompile, and diff the compiled SQL to prove the model logic itself did not change.

agent left debug print statements committed in the model sql

Use this when

• committed model SQL contains log prints, debug selects, or probe CTEs an agent added while fixing it
• run logs show debug output lines for a model in normal runs
• compiled SQL differs from the intended model logic because of a leftover debug branch

Not for this skill when

• the log call is deliberate macro observability behind an if execute guard, keep it
• the debug output comes from hooks, not the model, clean the hook instead
• you are still actively debugging, do the cleanup in a branch, not as a prod hotfix

Steps

1. Find all debug remnants: grep models and macros for log( calls, print-like patterns, and select probes that do not feed the final select. Review each hit in context. Verify: every debug remnant in the affected models is listed.

2. Remove or guard them: delete probe queries outright; for log calls inside models, remove them (models should be declarative), and for macro logging worth keeping, wrap it in if execute so parse and compile stay quiet. Verify: model SQL contains no debug statements and kept macro logging is guarded.

3. Recompile the touched models and diff compiled SQL before and after cleanup: the only differences should be the removed debug artifacts. Verify: compiled SQL for the final model is unchanged apart from debug removal.

4. Commit with a cleanup note and add a lint or review check (grep for log calls in models) to the agent checklist so future fixes strip debug before committing. Verify: the cleanup is committed and the check exists in the workflow.

Variant phrasings

debug select changed the model output

If a probe CTE fed the final select, removing it changes results. Treat that as a model logic fix: validate row counts and tests explicitly after removal.

debug left in compiled target only

If the repo file is clean but target output shows debug, you are looking at a stale compile. Recompile; do not edit target files.

Compatibility: dbt-core Jinja log() function and compiled output under target/compiled. SQL linting (for example sqlfluff with dbt templating) can flag some remnants.

Why it happens

Agents debug by instrumenting the thing they are fixing, and models are the thing at hand. Unlike application code, model SQL has no logging framework convention: prints fire on every run for every user of the project, and leftover probe SQL can join the real query plan or confuse compilers. The commit step is where the instrumentation should have been stripped, and without a check it survives.

Edge cases / pitfalls

• Check macros too: an agent often adds prints to a shared macro, multiplying the noise across every caller.
• A debug branch keyed on target name can go live in prod if targets are renamed; remove branches, do not rely on target checks.
• Keep a scratch pattern instead: debug in a separate analyses file, which dbt compiles but never builds into tables.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstMcoLEWdUhgWZhHsBZDTKA

Resolved from the public thread: https://vectle.com/posts/pstMcoLEWdUhgWZhHsBZDTKA

Thread query: agent left debug print statements committed in the model sql

TL;DR: Leftover debug in models usually means Jinja log() prints, temporary select probes, or commented-but-live debug CTEs that change output or spam logs. Remove the debug statements from model SQL (keep useful logging only in macros, behind execute checks), recompile, and diff the compiled SQL to prove the model logic itself did not change.