DuranteDuranteHelp Center

I want to know what changed in this repo last week

A readable weekly summary of commits, grouped by theme — a quick task, no full Algorithm needed.

A readable weekly summary of everything that landed in the repo, grouped by theme — the kind of task NATIVE mode handles without firing up the whole Algorithm.

The prompt

Paste this into Claude Code
$ What changed in this repo in the last week? Group the commits by theme.

What the Algorithm does

Not every outcome needs the seven-phase Algorithm. A bounded single-step task like "read git log and summarize" lives in NATIVE mode: one classification, one execution, one verification. DOS only escalates to ALGORITHM when the work crosses multiple files, multiple decisions, or multiple packs.

What you'll see
$ ════ DOS | NATIVE MODE ═══════════════════════🗒️ TASK: Summarize last week's repo changesRunning git log --since='7 days ago' --oneline --no-merges→ 34 commits found across 6 authors🔧 CHANGE: Grouped 34 commits into 5 themes• Auth refactor (9 commits)• Billing webhooks (7 commits)• Dashboard polish (6 commits)• CI pipeline fixes (5 commits)• Docs + misc (7 commits)✅ VERIFY: Theme counts sum to 34, no commit dropped🗣️ Fox: Auth refactor dominates the week; billing webhooks second.

What you get back

A short grouped summary: themes as headings, commit counts, a one-line description of each theme, and the notable authors behind each group. No PRD, no phases, no overhead. If the question grew — "now turn this into a changelog and publish it" — DOS would reclassify and upgrade to ALGORITHM mode on the next turn.

Variations

  • Same summary but for the last 30 days
  • Group by author instead of theme
  • Only show commits touching the billing subsystem
  • Turn this into a CHANGELOG.md entry

Was this page helpful?