Review, commit, and push local changes through the current branch's configured upstream. Use when you want to ship a deliberate commit without assuming a particular remote.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Commit reviewed changes and push only through the branch's configured upstream.
Confirm branch and upstream
BRANCH="$(git branch --show-current)"
UPSTREAM="$(git rev-parse --abbrev-ref --symbolic-full-name '@{upstream}' 2>/dev/null || true)"
test -n "$BRANCH" || { echo "Detached HEAD; create or check out a branch first"; exit 1; }
test -n "$UPSTREAM" || { echo "No upstream configured; choose the intended remote, then run: git push -u <remote> $BRANCH"; exit 1; }
case "$BRANCH" in main|master) echo "Direct pushes to $BRANCH are not allowed"; exit 1;; esac
printf 'Branch: %s\\nUpstream: %s\\n' "$BRANCH" "$UPSTREAM"
Do not push directly to protected branches such as main or master.
Review and validate
git status --short
git diff
git diff --cached
Run the relevant project checks documented by the repository before staging.
Stage, commit, and push
git add -- path/to/related-file
git diff --cached
git commit -m "<prefix>: <summary (imperative, concise)>"
git push
Use git add -A only when every pending item belongs in this commit. Split
unrelated work into separate commits instead of pushing it together.
git push uses the resolved upstream rather than assuming origin.feat, fix, refactor, perf, test, docs,
build, ci, chore, style, or revert.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Add an iOS App Clip target to an Expo app. Use when the user mentions App Clip, AASA, apple-app-site-association, appclips, smart app banner, or wants to ship a lightweight iOS Clip invoked from a URL alongside their parent app.
The English summary is being prepared. Showing the original description.
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
The English summary is being prepared. Showing the original description.
Add Agentation visual feedback toolbar to a Next.js project
The English summary is being prepared. Showing the original description.
Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking, leading), reduced-motion, or the design foundations (feedback, spatial consistency, restraint) behind Apple-style interfaces.
The English summary is being prepared. Showing the original description.
Derive and implement first-principles audio-coupled haptic and kinetic UI feedback. Use when designing, reviewing, or coding haptics/audio for mobile apps, native iOS/Android, React Native/Expo, SwiftUI, games, detent pickers, toggles, sliders, page curls, scroll gestures, wallet/signature flows, Solana transactions, backend/realtime state changes, confirmations, settlements, and semantic UI events where feedback should follow signal math instead of ad hoc vibration calls.
The English summary is being prepared. Showing the original description.
Babysit a GitHub pull request during a user-approved monitoring window by polling review comments, CI checks/workflow runs, and mergeability state. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and report fresh review feedback. Use when the user asks Codex to monitor a PR, watch CI, handle review comments, or keep an eye on failures and feedback on an open PR.
The English summary is being prepared. Showing the original description.