// gitlab
2026-02-18
What it actually takes to wire automated security review into every merge request on a GitLab project — token scopes, webhook, severity tuning, and how to keep the noise down on the first week.
Read note
// review model
2026-02-11
Whole-tree scanners have their place, but day-to-day they overload the team with old findings. Diff-only review stays focused on the change being shipped — fast, cheap, and close to the merge request.
Read note
// findings
2026-02-04
A short tour of the bug classes that show up clearly in the diff but slip past traditional static scanners — with annotated examples from real merge requests and the prompt patterns CodeGuards uses to catch them.
Read note
// audits
2026-01-28
Audit prep usually means someone reconstructing months of review history from chat threads. If every change already gets a recorded security review, half of that work is just… already done.
Read note
// signal
2026-01-21
Every codebase has its own rules. Generic suppressions don't survive a refactor. Per-repo memory does — accept once, leave a note about the internal policy, and the same pattern stops nagging the team forever.
Read note