Pass --no-project to the Pre-Commit Snippet's uv run Hooks

[ptr727]

The pre-commit snippet ran its prose and EOL hooks as a project-scoped uv run, which writes a uv.lock in a directory whose pyproject.toml has none. Committed, that lock reclassifies a lint-only or pip-form directory as the uv form of the build profile.

• Both uv run hook entries in catalog/snippets/pre-commit/.pre-commit-config.yaml now pass --no-project, matching the "Lint: Prose" and "Lint: EOL" tasks in catalog/snippets/configs/vscode-tasks-python.json. The helpers they run import only the standard library.
• Checked with a constructed directory holding a pyproject.toml with only a [tool.ruff] table: the old entries wrote a uv.lock there, the new ones did not, and both helpers ran.
• No other surface states these entries. A tree-wide search found only the two VS Code tasks, which already carry the flag.

A local strict review pass noted that --no-project also ignores the repository's requires-python when choosing an interpreter. That matches the VS Code tasks and the Husky snippet, which runs py -3 or python3 directly. The one consequence it traced, the prose gate silently skipping the AST checks on a file its interpreter cannot parse, is in code this change does not touch, so it is filed as #2163.

Closes on promotion: #2148

🤖 Generated with Claude Code

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Repository: ptr727/ProjectTemplate/.coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 1fdd53a2-a7b4-4786-9aa5-5732cf55d7f4

---

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.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (develop@a0806e3). Learn more about missing BASE report.

Additional details and impacted files

@@            Coverage Diff             @@
##             develop    #2164   +/-   ##
==========================================
  Coverage           ?   56.47%           
==========================================
  Files              ?       16           
  Lines              ?     7455           
  Branches           ?        0           
==========================================
  Hits               ?     4210           
  Misses             ?     3245           
  Partials           ?        0           

Flag	Coverage Δ
python-3.13	56.47% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Copilot]

Copilot review overview

🟢 Approval recommended

The two-line change adds a well-understood flag that exactly matches the established sibling VS Code task pattern, and all PR description claims were verified against the tree.

Review effort: Balanced
Findings: None

What changed in this PR

This PR fixes a subtle side effect in the pre-commit framework catalog snippet. Its prose and EOL doc-gate hooks previously ran as a project-scoped uv run, which writes a uv.lock into any directory whose pyproject.toml lacks one. Once committed, that lock reclassifies a lint-only or pip-form directory as the uv form of the build profile (per the audit's python.profile.detect), so the hooks silently mutated repository classification. Adding --no-project prevents the lock from being written, and aligns the snippet with the sibling "Lint: Prose" and "Lint: EOL" VS Code tasks, which already carry the flag.

Changes:

• Add --no-project to the prose-gate hook's uv run python hub-fetch-run.py ... prose_lint.py entry.
• Add --no-project to the eol-gate hook's uv run python hub-fetch-run.py ... repo_gate.py entry.

I verified: these are the only two uv run doc-gate entries in the snippet; the referenced VS Code tasks (vscode-tasks-python.json:182,193) already use run --no-project python; and the Husky snippet runs the same doc gates directly via py -3/python3, so it is unaffected. The changes match the established pattern, and no documentation surface describes these entries in a way that now needs updating.

File	Description
catalog/​snippets/​pre-commit/​.pre-commit-config.yaml	Adds --no-project to both uv run doc-gate hook entries so they no longer write a uv.lock, matching the VS Code Lint tasks.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.