Why developers use Blamely

Blamely is for anyone who ships code with an AI assistant in the loop and wants facts, not vibes, about who (or what) wrote what. Below is how individual developers, teams, and leads typically use it.

For individual developers

  • Honest self-review — Before you open a PR, see how much of the diff is AI vs you. That helps you decide where to add tests, comments, or a second look.
  • Skill and habit tracking — Over weeks, History shows how your mix of AI and human lines shifts by project or branch — useful if you are calibrating how you use Copilot, Cursor, or JetBrains AI.
  • Less impostor noise — When a feature “felt” mostly AI-assisted, you can verify the split instead of guessing in retro or standup.

For code review and quality

  • Targeted review — Reviewers can prioritize files or commits with a high AI percentage for security, correctness, or style — without banning AI outright.
  • Explainable diffs — “This commit is 40% AI” is easier to discuss than subjective claims; it complements git blame (committer) with authorship in the editor (human vs assistant).
  • Regression hunting — When something breaks, attribution helps you see whether risky lines cluster in AI-heavy regions worth double-checking.

For teams and tech leads

  • Shared vocabulary — Teams agree on what “AI-heavy” means using the same numbers from the same tool, inside the same IDE they already use.
  • Velocity and risk — Coding time vs AI wait time and model breakdowns (where available) support planning: capacity, tool choice, and training — not surveillance theater, if used transparently.
  • Policy alignment — Organizations that require disclosure or limits on AI-generated code can ground guidelines in measurable per-commit or per-file stats instead of checkbox compliance only.

For compliance and audit

  • Evidence in git — Optional git notes and report.yml under .git/blamely give a durable record tied to commits (see How it works).
  • Local-first — Core attribution runs in the IDE on your machine; you choose what to share upstream. The website supports docs, account, and licensing where your company needs them.

What Blamely is not

  • It is not a replacement for code review, security scanning, or human judgment.
  • It does not “score” developers as good or bad — it attributes lines so you decide norms and follow-up.