Stats
Actions
Tags
How this command is triggered — by the user, by Claude, or both
Slash command
/expo:finishThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Finish Finalize the current branch by adding a changelog entry and generating a PR description. This combines `/expo:changelog` and `/expo:pr-summary` into a single step. ## Steps 1. Run the changelog workflow: derive the entry from the branch diff, look up the PR number and author, and add the entry to the appropriate `CHANGELOG.md` file(s). Follow all rules from the changelog command. 2. Run the PR summary workflow: generate a brief PR description from committed changes following the expo PR template (Why / How / Test Plan / Checklist) and copy it to `pbcopy`. Follow all rules from t...
Finalize the current branch by adding a changelog entry and generating a PR description. This combines /expo:changelog and /expo:pr-summary into a single step.
CHANGELOG.md file(s). Follow all rules from the changelog command.pbcopy. Follow all rules from the pr-summary command.npx claudepluginhub vonovak/expo-claude-plugin --plugin expo/finishCreates a pull request with comprehensive description following repo best practices, loading config, verifying git state, summarizing changes, gathering user input, pushing branch, and opening PR.
/finishInvokes jig:finish skill to finalize tasks when implementation is complete, all tests pass, and a decision is needed.
/finishRuns the full completion pipeline: verifies build, commits to git, simplifies code, commits again, verifies build, and rebases onto upstream.