The summarizer: PR text from a finished task

Purpose

After the code is written and checked, someone has to explain it. This read-only role does that, so a reviewer opens a pull request with context instead of a bare diff.

It runs after verification and before the work moves to review, as step 7 of the pipeline.

What it produces

It writes three texts: a summary of the change, the PR description and a changelog entry. It also mints the commit message in Conventional Commits form, in English, for example feat(homepage): ABC-123 remove the secondary button. That message becomes the squash subject and the PR title.

When the task title or description holds a ticket reference, such as a Jira or Linear key, an issue number or an issue URL, the pipeline passes it along. It is placed after the colon of the subject.

A safety net at mark-done

The pipeline does not trust the message blindly. If the minted subject is not conventional, mark-done builds one from the task type and title, so a fix gets fix: and a feature gets feat:.

A repository that declares its own commit convention, for example through a commitlint configuration, keeps the minted message as written.

Large diffs

At or below 512 KB, the cumulative diff is inlined in the prompt. Above that, the prompt carries a per-file diffstat and the role reads the changed files itself. A large change does not overflow the model context.

Screenshots

The role also declares which screens are worth capturing. The pipeline shoots only those, at most 8 per platform, and the images are embedded in the PR body at mark-done.