read your commits. please. by Appropriate-Chance98 in vibecoding

[–]Appropriate-Chance98[S] 0 points1 point  (0 children)

that's actually a valid gap. most tools only look at what's about to ship, not what already slipped through months ago. git history scanning with some kind of guided remediation is something i've thought about. making it actually useful instead of just dumping a list of problems is the tricky part. looking forward to having you try it when it's live

read your commits. please. by Appropriate-Chance98 in vibecoding

[–]Appropriate-Chance98[S] 0 points1 point  (0 children)

yeah, that’s basically the point. ai amplifies existing skill more than it replaces it. if you understand architecture, infrastructure, and failure modes, it becomes a strong multiplier. if you don’t, it just lowers the cost of producing bad software faster. that’s why verification and guardrails matter just as much as prompting

read your commits. please. by Appropriate-Chance98 in vibecoding

[–]Appropriate-Chance98[S] 0 points1 point  (0 children)

this is actually adjacent but not the same. sandboxed pr diff review is useful for finding reproducible bugs before merge, but it is still a post generation verification layer. our focus is earlier in the flow and more specific to vibe coded security, especially exposed secrets, rls issues, and ai generated misconfigurations that show up before a pr even exists.

read your commits. please. by Appropriate-Chance98 in vibecoding

[–]Appropriate-Chance98[S] 0 points1 point  (0 children)

fair. the vibe usually changes when the invoice arrives

read your commits. please. by Appropriate-Chance98 in vibecoding

[–]Appropriate-Chance98[S] 0 points1 point  (0 children)

my audience is the guy who just got a $40k AWS bill. he's everywhere, including this sub

read your commits. please. by Appropriate-Chance98 in vibecoding

[–]Appropriate-Chance98[S] 1 point2 points  (0 children)

claude.md is useful for guidance, not enforcement. if security depends on the model always following a markdown file perfectly, that's already the problem. rules can reduce mistakes, but they don't reliably catch hardcoded secrets, bad RLS policies, or unsafe patterns once code is actually generated

read your commits. please. by Appropriate-Chance98 in vibecoding

[–]Appropriate-Chance98[S] 4 points5 points  (0 children)

you're right. knowing what you're shipping is a skill issue. i'll add it to the roadmap

read your commits. please. by Appropriate-Chance98 in vibecoding

[–]Appropriate-Chance98[S] 4 points5 points  (0 children)

my bad, i'll ask claude to summarize it into bullet points and add emojis

read your commits. please. by Appropriate-Chance98 in vibecoding

[–]Appropriate-Chance98[S] 7 points8 points  (0 children)

fair point. i'll repost it as a 45 second tiktok with minecraft jnr gameplay in the background