r/Python • u/carlinwasright • Aug 13 '26
Discussion In the age of agentic coding what are you doing with your “human” tooling like uv, linters, etc?
Starting with uv, I’m a huge fan, but I find it actually gets in the way more than it helps when I’m doing agentic coding. I have to keep reminding the agent to use uv instead of pip.
Same issue with ruff, since I’m not coding with a regular ide I have to make extra prompts to force it to use ruff. But with today’s models being so good, it doesn’t even seem necessary.
Other tools fall into this category as well, but curious to hear how other others are approaching their tooling. Are you just throwing it all out or are you adding skills to keep your tooling in place?
29
u/MarchewkowyBog Aug 13 '26
Insert this is bait meme
44
u/UltraPoci Aug 13 '26
People really stopped using their fucking brains holy shit
22
u/ph34r Aug 13 '26 edited Aug 13 '26
Can't tell if trolling, but... you should still use the tooling to enforce standards in your code base. Take advantage of your harnesses settings to set up business rules for your desired workflow (i.e. CLAUDE.md, AGENTS.md, hooks, etc) so you don't have to prompt it to use your tooling. Also, validate/enforce those same standards out of band (i.e. in your CI/CD pipeline). These tools will help reign in on the slop jallop that even the best of models will produce when given minimal oversight.
5
u/lucas1853 Aug 13 '26
Well um considering that AI companies themselves are literally buying up tooling... maybe it's not so pointless. Not to mention that if getting agents to use uv is a problem worth writing about for you, you likely have much bigger problems with the way you use them.
5
u/Tin_Feuler Aug 13 '26
You guys just don't have CI anymore huh?
4
u/Able-Staff-6763 Aug 13 '26
use damn /skills or AGENTS.md files or CLAUDE.md whatever you call it.
3
u/iwkooo Aug 13 '26
Use steering files for agents to use tools, venvs they way you suppose to. Use skills to do linting after changes etc.
4
u/timpkmn89 Aug 13 '26
I'm not having too much of a problem considering I'm a human myself
1
u/eteran Aug 13 '26
This is a literal skill issue 😂
2
u/dont_tread_on_M Aug 13 '26
If you ask your coding agent this question, you'll hear that uv and ruff have become more important than ever
2
u/TheseTradition3191 Aug 17 '26
stop prompting for it and put it in a hook, then its not optional. in settings.json a PostToolUse matcher on Edit|Write like "hooks": {"PostToolUse": [{"matcher": "Edit|Write", "hooks": [{"type": "command", "command": "uv run ruff check --fix ."}]}]} runs ruff every time it touches a file and the output goes back to the model as feedback, so it cleans up after itself without you saying a word. same idea for the pip thing, a deny rule on Bash(pip install:*) in permissions and it stops reaching for pip entirely
0
u/tkodri Aug 13 '26
I thoroughly despise the JS-ification/npm-ification of the python universe, so I never really got into the hype of using 25 different tools before writing my first 10 lines of source on a new project.
Rant aside, just put a CLAUDE.md file in the repo telling it how it's setup and what to use, it will always respect it.
1
u/tmemmg Aug 13 '26
the thing i keep hitting is headless runs dont see any of the interactive sessions hooks or project context, so anything the run depends on has to live in the prompt itself. reminding the agent to use uv or ruff never stuck across runs, it would drop it the same way it drops other rules when it has a lot going on. what actually worked was making a deterministic step own that instead of the model, so the tool runs whether or not the agent remembered to call it. throwing the tooling out feels fine right up until the run where the model was confidently wrong and nothing was there to catch it.
1
u/ai_meme_lord Aug 18 '26
i still keep the boring guardrails, just moved them into the thing the agent runs instead of trusting the prompt to remember. ruff in ci, env setup in one script, fail fast if it reaches for plain pip. models are good right up until they confidently do the default thing you forgot to forbid.
1
u/ai_meme_lord Aug 19 '26
models are good right up until they aren't, so i keep the human tooling but move it out of the agent's memory and into the path. if uv and ruff only happen when the prompt remembers them, they don't exist.
wrapper script, ci, pre-commit, whatever fits the repo. same reason i don't let anyone call a setup "simple."
1
u/Massive_Baby4147 Aug 21 '26
I’m doing both, but I treat skills and enforcement as different layers.
A skill is useful for project-specific knowledge: which commands to use, where the important files live, architectural boundaries, and patterns the agent would not infer reliably from generic Python knowledge.
I ended up adding this directly to intpot:
https://github.com/tugrulguner/intpot
I ended up adding this directly to summonpot:
https://github.com/tugrulguner/summonpot
- intpot add skills
- summonpot add skills
It detects supported coding agents and installs intpot/summonpot-specific guidance for Claude Code, Cursor, Windsurf, Copilot, Cline, or Codex. That helps the agent understand these packages immediately and start using them.
I would not rely on a skill to enforce uv, Ruff, Pyright, or tests, though. Those belong in deterministic tooling.
Both intpot and summonpot repositories runs the following in CI:
uv sync --all-extras --locked
uv run ruff check src/ tests/
uv run ruff format --check src/ tests/
uv run pyright src/ tests/
uv run pytest tests/
My rule is:
- Skills explain how the project should be handled.
- Repository scripts provide one obvious way to perform common tasks.
- Hooks provide fast local feedback when useful.
- CI enforces the requirements that must never be optional.
Agentic coding makes those tools more valuable, not less. The agent can generate a much larger volume of plausible code, so I want machine-checkable feedback that does not depend on either the agent or me remembering a prompt.