How do you make a sanity script version-conscious?

Short Answer

Don't hardcode command names or default behaviors into a sanity script — both can silently change between tool releases, and a script that assumes yesterday's defaults can pass or fail for the wrong reasons. A dependable script asks the installed tool what it actually supports before running: use get_design_checks to confirm which check bundles exist in this release.

Technical Explanation

• Use man on the specific command to confirm its current syntax and options rather than relying on memory or an older script as a template.
• This turns the script from "fragile and release-specific" into "self-adapting" — it queries the live tool for ground truth instead of assuming the environment matches whatever version it was originally written against.

What To Check

• Warning sign: A copied script calls an unavailable check name or relies on changed defaults.
• Inspect: Compare one named object across the related reports; the same object should tell a consistent story.
• Correct: Gate optional checks by supported names, record the tool version, and keep release-specific logic explicit.

Healthy, Suspicious & Hard-stop Results

• Expected: Use get_design_checks to confirm available check bundles and man to confirm syntax in the installed release.
• Stop before floorplanning when required logic or timing coverage is missing or unexplained.

What The Interviewer Is Testing

Be ready to explain why this matters before floorplanning.

Follow-up Question & Model Response

Model response: “I would save the report, inspect one affected object in the correct block and scenario, and make or request this correction. ”