mitodl/agent-kit/validate-before-commit

Validate Before Commit

Do not declare a task done until the full validation sequence has passed. Run these checks proactively — do not wait for the human to ask.

Standard sequence

# 1. Linting, formatting, and basic static checks
uv run prek run --all-files
 
# 2. Type checking
uv run mypy <package_or_src_dir>
 
# 3. Infrastructure plan (if Pulumi files were changed)
pulumi preview --stack <stack-name>

mitodl repositories run their hooks with prek, which reads the same .pre-commit-config.yaml (or prek.toml) that pre-commit did. Use the command for the repository's prek pin:

In a repository with .github/workflows/autofix.yml, the same hooks run in CI as the prek check. When the hooks' only problems are ones they fixed themselves, autofix.ci commits those fixes to the PR, except under .github/. If any hook still fails, nothing is committed and the check stays red. Running the hooks locally first avoids both.

Rules

• Run the hooks before mypy; they may auto-fix formatting that would

otherwise produce mypy noise.

• If the hooks auto-fix files, stage the changes and re-run them to confirm

every hook passes cleanly.

• mypy errors are blocking — do not leave type errors for the human to clean up.
• pulumi preview output must be reviewed: unexpected replacements or deletions

are bugs, not acceptable side effects.

For Dagster / dg changes

After modifying assets, sensors, or code location structure, also confirm the workspace loads cleanly:

dg check

Interpreting failures

Read the full error output before proposing a fix. Do not apply a speculative patch without understanding the root cause — iterating blindly on the same error multiple times is worse than pausing to diagnose.