Add dev-report skill

[delpicorp]

Adds dev-report to Communication & Writing, in alphabetical order. README entry only — the skill lives in its own repository, like article-extractor, brainstorming, and family-history-research in the same section.

What problem it solves

You finish a long Claude Code session. A dozen files changed, a bug got fixed, and several implementation calls were made along the way. Ask "what did we do today?" and the summary is accurate but written for someone reading the diff alongside it — file names, function names, a change list. Ask for it "simply" instead and the reasoning goes out with the jargon, leaving something short you still can't act on.

dev-report explains the session in plain language and reports four things: what was built or changed, why that approach was chosen, what is still unfinished or unverified, and what to do next. Technical terms aren't removed — they're explained the first time they appear, so the reasoning survives intact.

Two rules do most of the work. Every finding leads with the raw artifact — the actual log line, the actual count — before it gets explained. And the section on how a problem was solved is required to name the option that was rejected and what would have gone wrong, which is the only way to check a technical decision you can't read yourself.

Who uses this workflow

People building their own products with Claude Code — vibe coders, indie hackers, solo founders — who need to understand what happened in a session before deciding what's next. Also developers who owe an end-of-session explanation to a founder, client, or PM who doesn't read code.

Attribution

Our own working practice — the end-of-session write-up we were doing by hand, turned into a skill. Not adapted from anyone else's workflow.

Example

/dev-report
/dev-report this week
/dev-report just the payment work
/dev-report keep it short, she only has a minute

Opening of a worked example that ships in the repo (illustrative, not a real customer session):

Today was supposed to be clearing four small items off the backlog. I got through two of them, then found that about one in six customers hasn't been receiving their order confirmation email since the payment provider upgrade three weeks ago. That's fixed and live now. The other two backlog items are untouched.

Notes

• The skill is deliberately explicit-only. It does not hijack a casual "what did you just do?" — that question wants a two-line answer, and answering it with a formal report is its own kind of failure.
• Reports come out in whatever language the command was typed in; localized command aliases ship for Korean, Japanese, and Spanish. File paths, function names, and error messages always stay in their original form.
• Installs as a Claude Code plugin (/plugin marketplace add delpicorp/dev-report) or as a plain skill via git clone. Tested on Claude Code. MIT licensed.

Updated 2026-08-04: reworded the entry and this description to lead with what the skill does rather than who it's for.