Skip to content

Tohuhono/Oberon / .agents/skills/commit

commit

Verified

Update the current branch by ensuring all branch changes are included, adding required changesets, then committing and pushing. Use when user asks to commit, update a PR, refresh an open PR, or push latest work to the current PR branch.

FileKindSize
SKILL.mdskill md2.5 KB
---
name: commit
description:
  Update the current branch by ensuring all branch changes are included, adding required changesets,
  then committing and pushing. Use when user asks to commit, update a PR, refresh an open PR, or
  push latest work to the current PR branch.
argument-hint: What should be included in this PR update?
---

# Commit changes

Commit the current work state and update pull request. This workflow assumes implementation and
validation are already complete.

## When to Use

- User asks to "commit", "update PR", "refresh PR", or "push latest changes"
- There is already an open pull request for the current branch

## Procedure

1. Confirm branch context
   - Capture current branch and working tree status.
   - Include all changes, even if they are from the user or out of scope of the task
2. Derive work metadata
   - Follow [METADATA](../../METADATA.md).
   - Summarise completed work outcomes, not workflow mechanics.
3. Ensure release metadata
   - Add or update a [changeset](https://github.com/changesets/changesets) for new package changes.
4. Commit
   - Stage intended files.
   - Commit with a very concise summary of completed work.
   - Avoid process wording like "update PR" or "latest changes".
5. Push current branch
   - Push to `origin` on the same branch.
   - Do not create a new branch.
   - Do not create a new PR.
6. Update PR
   - If the scope of the PR has increased, rewrite PR title/description to include the completed
     work outcome.

- Keep PR body to one sentence.
- Be very concise.

7. Report outcome
   - Share branch name, commit SHA, and push result.
   - If blocked, report the blocker and next required manual action.

## Decision Points

- Include all user changes, update scope if required
- Do not run validations or checks; assume the code is correct
- Always generate concise work-focused metadata via [METADATA](../../METADATA.md); do not ask for
  wording.
- Commit summary should be extremely brief; details are already captured in the changeset.
- Missing changeset: add/update changeset before committing.
- Push rejected (non-fast-forward): pull remote and merge, resolve conflicts, then retry push.
- Auth/permission error: stop and report exact failure.

## Completion Checks

- Current branch is preserved (no branch switch)
- All intended branch changes are included
- Changeset is present for new package changes
- Commit and PR metadata describe completed work outcomes (not workflow mechanics)
- Push to current branch succeeds
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall