{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreih3qum6ytqf4eb3jzdzji2i6qjbk3ikjhxce5bcl7msdzjk6x7isu",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mjam346ogqz2"
  },
  "path": "/t/how-to-filter-out-vibe-coded-dependencies/13918#post_12",
  "publishedAt": "2026-04-11T17:03:27.000Z",
  "site": "https://discourse.haskell.org",
  "textContent": "btw i have customInstructions and CLAUDE.md “donts” that explicitely say “no co auth”. If i get help from google or stack overflow or forums, i dont add \" Co-Authored-By Haskells discourse forum\" hell no. I also am pretty strict to review commits and if some contain co-auth crap i might rewrite the whole history if im not 100% committed yet. Or shed a tear and move on if it reached master. Its MY responsibility. It doesnt HELP to blame or credit claude code. Think about, if you use a special keyboard for development, do you attribute every commit with “co developed with Foobar keyboard”? nope. Claude code is just a tool. It wont take over the world. (just improve the speed of which we get new libraries, which before was EXTREMELY tedious and needed at least an awesome set of devs, or a very very persistent single one). (yes i got a bit carried away there maybe)",
  "title": "How to filter out vibe-coded dependencies"
}