[BugFix] Add pre-commit to requirements-dev.txt

[asaadkhaja99]

As reported in #1609, adding pre-commit to the requirements-dev.txt would simplify local development setup.

Summary by CodeRabbit

• Chores
  • Added pre-commit (>=4.0.0) to development dependencies to enable additional pre-commit tooling and checks.
  • This change affects developer workflows only; there are no runtime or build behavior changes visible to end users.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[github-actions]

👋 Hi! Thank you for contributing to the TileLang project.

Please remember to run pre-commit run --all-files in the root directory of the project to ensure your changes are properly linted and formatted. This will help ensure your contribution passes the format check.

We appreciate you taking this step! Our team will review your contribution, and we look forward to your awesome work! 🚀

[coderabbitai]

📝 Walkthrough

Walkthrough

Added pre-commit>=4.0.0 to requirements-dev.txt; this is a development-only dependency and does not change runtime or build behavior.

Changes

Cohort / File(s)	Summary
Development dependency requirements-dev.txt	Added pre-commit>=4.0.0 to development requirements

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related issues

• [BUG] Pre-commit setup fails because pre-commit not in requirements-dev.txt #1609: Addresses the previously missing pre-commit development dependency.

Poem

🐰 I hopped by the dev tree, found a hook so neat,
I tucked pre-commit in, now checks are complete.
A nibble of lint, a whisker of test,
Clean commits ahead — may our repo rest. ✨

Pre-merge checks

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: adding pre-commit to requirements-dev.txt to fix a development setup issue, which matches the changeset content.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0a1f133 and f666a57.

📒 Files selected for processing (1)

• requirements-dev.txt

🚧 Files skipped from review as they are similar to previous changes (1)

• requirements-dev.txt

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

Fix all issues with AI Agents 🤖

In @requirements-dev.txt:
- Line 9: The dependency entry "pre-commit" in requirements-dev.txt should be
pinned for reproducibility and to avoid config-migration breaking changes;
update the line containing the literal symbol pre-commit to include a version
specifier such as pre-commit>=4.0.0 (or pin to the known stable
pre-commit==4.5.1) so CI/dev envs install a predictable, compatible release.

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7cfd087 and 0a1f133.

📒 Files selected for processing (1)

• requirements-dev.txt