danielmiessler

Deeds — AI skill for Claude Code

AI community

A CLI and Claude Code plugin that reads every commit's diff and counts what actually got better: new capabilities, fixes, and upkeep.

How to install Deeds

This entry records only its repository, not the path inside it, so there is no exact command to give. Open danielmiessler/Deeds and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Deeds does

A CLI and Claude Code plugin that reads every commit's diff and counts what actually got better: new capabilities, fixes, and upkeep. A way to measure work done with AI that doesn't depend on counting PRs.

Alternatives in AI

  • Impeccable — The design language that makes your AI harness better at design 13.9k ★
  • Better Harness — Review this project's AI coding workflow with Better Harness and generate a durable report 2.1k ★
  • VibeMeter — A project to measure costs for Cursor and other AI provider 379 ★

README

The workdeeds.ai home page: A New Way to Measure Work Done with AI

Deeds

Measure the work in a code repo by what got better, not by how many PRs were opened.

workdeeds.ai Latest release MIT license

Pull requests and commit counts measure activity. They show that code changed, not whether the product got better. A refactor, a revert and a typo fix count the same as a new feature, and someone building alone with AI agents may never open a PR at all.

Deeds reads the diff of every commit in a window and asks what that change did to the product. A change that made it better is a **deed**, and every deed is one of three kinds:

Kind What it means Example
cap A capability gained or deepened. The product can do something it couldn't before, or does an existing thing more fully. added CSV export to reports
fix Something moved from broken to working. Security fixes count here. stopped logging session tokens
tend Upkeep users never see: refactors, dependency bumps, performance work, tests. bumped hono to 4.6

Renames, reverts and busywork produce no deeds. Commit messages are never read, so a commit called "feat: X" only counts as a cap if its diff adds one. The three counts stay separate and are never blended into one score. The argument for all of this is at [workdeeds.ai](https://workdeeds.ai).

What you get

A real run over the last 90 days of [golang/go](https