changelog-summarizing

Changelog Summary Post

Generate summary posts about repository changes since a given date. Produces two separate outputs: one formatted for Discord (markdown) and one for Slack (mrkdwn).

Requirements

• Working directory is this repository
• User provides a date (absolute or relative)

Hard Constraints

• Main branch only. Only analyze committed history on the main branch. Ignore uncommitted files, staged changes, untracked files, and working tree state entirely. The skill operates as if in a clean checkout.
• Repository URL: https://github.com/shopwareLabs/ai-coding-tools. Use this for constructing plugin links.

Phase 1: Parse Date

Extract the date from the user's input. Accept absolute dates ("2026-04-01") and relative dates ("last Monday", "two weeks ago").

If no date is provided, ask:

What date should I summarize changes from? (e.g., "2026-04-01" or "last Monday")

If the date is in the future, inform the user and stop.

Phase 2: Discover Commits

Commits on main matching the requested date:

if [ -z "$since" ]; then
  echo "(no date supplied at skill invocation)"
else
  git log main --since="$since" --format="%H %s" --no-merges
fi

If no commits are listed above, tell the user and stop:

No commits found on main since .

If the listing reads "(no date supplied at skill invocation)", ask the user for a date (Phase 1) and re-invoke the skill with the date as the first argument.

Use the listed hashes as the input to Phase 3.

Phase 3: Analyze Each Commit

For every commit hash from Phase 2, run:

git show <hash>

For each commit, extract:

1. The full commit message (intent)
2. The diff (actual code changes)
3. The conventional commit scope from the subject line (if present)

Analyze both the message and the diff to understand what actually changed and why. The message states the intent; the diff confirms what happened. Use both to produce an accurate summary.

Phase 4: Group and Cluster

Group by scope: Parse type(scope): subject from each commit's subject line. Group commits by their scope value. Commits without a scope go into a "General" group.