parad0x0n

7 ms·

1. 1.▲
   by parad0x0n 6mo ago

   Thank you!
2. 2.▲
   by parad0x0n 7mo ago

   that's another option of course. But it's definitely easier to setup all these checks and linter tests with a skill file vs git hooks and actions
3. 3.▲
   by parad0x0n 7mo ago

   what danger?
4. 4.▲
   by parad0x0n 7mo ago

   yeah I guess figuring out how AI and your team can optimally work together is not that straightforward.. probably every engineering team is trying to figure that out atm :D but if we already let AI write reviews, they should at least be as
5. 5.▲
   by parad0x0n 7mo ago

   fair point. I think they should ALSO be in your CLAUDE.md. Doing Claude reviews with the exact same instructions still makes sense because the PR itself is often a co-production between AI and the human who gives the instructions (and in th
6. 6.▲
   What to Put in a Claude Code Skill for Reviewing Your Team's Code(everyrow.io)

   9 points by parad0x0n 7mo ago|13 comments
7. 7.▲
   by parad0x0n 7mo ago

   storing the classification definitely makes sense! We re-use the classification for the different merge attempts in the same run but do not store it because mostly we work with different data every time
8. 8.▲
   by parad0x0n 8mo ago

   So fuzzy matching only makes sense if you expect two columns having the same data more or less, otherwise you can skip that step. And then you have to pick a threshold -> if similarity of strings is above that threshold, it's a matc