would PostToolUse be a better place to do it than pre-commit? (trigger on `"^(Edit|Write|MultiEdit)$"`)
for lint issues that are autofixable, the tool use can trigger formatting on that file and fix it right away
for type issues (ts, pyright), you can return something like `{\"hookSpecificOutput\":{\"additionalContext\":$escaped},\"continue\":true}"` to let the edit complete but let Claude know that there are errors to fix next turn
thanks i've not used PostToolUse but will checkout. i'm excited about Rust's autofixable issues promise. curious how effective they are, and how deep of a issue can they solve
I have a 6 Pro that I got in November. AccuBattery says my health is at 99%. I use my phone for probably an hour a day and charge every other day.
You don't let your phones sit on their chargers while at 100% battery, do you? I'm fairly sure that's what killed the batteries of my last two phones. My Pixel 3 was working fine until I started working from home and the phone rarely left the charger. After 3 months, the battery started swelling.
Wrote this a while ago and continues to feel relevant as I'm reviewing pull requests from newer teammates and staring at force-pushed commit trying to figure out what changed between now and when I last reviewed it
(Title in submission is the title I originally intended and submitted to freeCodeCamp. Their editor changed it to what it is now ("How to" and "keep your code reviewers happy"). I then edited it back to what I originally submitted. The editor then overrode my edit and reverted it back )
for lint issues that are autofixable, the tool use can trigger formatting on that file and fix it right away
for type issues (ts, pyright), you can return something like `{\"hookSpecificOutput\":{\"additionalContext\":$escaped},\"continue\":true}"` to let the edit complete but let Claude know that there are errors to fix next turn
reply