Hacker News
new
|
past
|
comments
|
ask
|
show
|
jobs
|
submit
login
simlevesque
3 months ago
|
parent
|
context
|
favorite
| on:
Unix philosophy and filesystem access makes Claude...
A tip for everyone doing this: pipe the linters' stdout to /dev/null to save on tokens.
maleldil
3 months ago
[–]
Why? The agent needs the error messages from the linters to know what to do.
jamie_ca
3 months ago
|
parent
[–]
If you're running linters for formatting etc, just get the agent to run them on autocorrect and it doesn't need to know the status as urgently.
maleldil
3 months ago
|
root
|
parent
[–]
That's just one part of it. I want the LLM to see type checking errors, failing test outputs, etc.
ozim
3 months ago
|
root
|
parent
[–]
Errors shouldn’t be on stdout ;)
dymk
3 months ago
|
root
|
parent
[–]
“Errors” printed by your linter aren’t errors, they’re reports
ozim
3 months ago
|
root
|
parent
[–]
So if I want my CICD break on linter errors I have to implement parsing of stdout?
I'd rather have it breakout of the box by going to stderr.
Guidelines
|
FAQ
|
Lists
|
API
|
Security
|
Legal
|
Apply to YC
|
Contact
Search: