Scene picks
Review the diff, then commit
A test, a review, a commit message, then a changelog if a human will read it.

Why these
These four are a sequence, not a toolbox. Running the changelog skill on an uncommitted experiment writes release notes for work you may still throw away.
Install in this order
When the change is logic or a bugfix. Skip it for a layout tweak. The skill itself says UI layout is a poor fit, and exploratory work should be a spike first.
On the diff, before you commit. It asks for a verdict. A review with no verdict is a summary.
When you are ready to commit. Conventional Commits, and it wants you to look at the staged diff for secrets before the message.
Only after the commits exist, and only if a user will read the notes. Do not run it on a private branch.
Not for this
CodeQL, which needs a database you build first. Jira, which needs an account. pr-creator, which follows Gemini CLI's title check and will nag you on any other repo.