菜单
Push git changes to remote with full workflow including status check, staging, committing, and pushing. Use when the user asks to push changes, push up code, or sync with remote. Includes safety check to prevent pushing directly to main branch.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Create a demo user and company on local Panda via curl. Authenticates against the local dev server, submits the demo account form, and returns login credentials. Use when the user asks to create a local user, demo account, demo company, or needs a test account on local Panda.
Publish implementation plans to Notion instead of local markdown. Use whenever creating an implementation plan, architecture plan, spike plan, migration plan, or any planning document. Replaces local docs/ output with a Notion page under the Planning docs page.
List and remove old git worktrees sorted by last activity. Shows when each worktree was last touched and lets the user pick which ones to remove. Also cleans up the associated local branch and AVD emulator if one exists. Use when the user says "cleanup worktrees", "remove worktrees", "delete old worktrees", "clean up branches", or "list worktrees".
Delete all Android emulators created by the build-android-app skill. Finds AVDs matching the {project}_{branch} naming convention, shuts down any that are running, and deletes them. Use when the user says "cleanup emulators", "delete emulators", "remove avds", or "clean up android emulators".
Build, install, and launch an Android app on an emulator after code changes. Auto-detects Gradle wrapper, build variant, application ID, and emulator. Use after making code changes to verify compilation, when the user says "build the app", "run the app", "launch on emulator", or when a workspace rule says to build after changes.
Build, install, and launch an iOS app on the Simulator after code changes. Auto-detects project file, scheme, bundle ID, and simulator. Use after making code changes to verify compilation, when the user says "build the app", "run the app", "launch on simulator", or when a workspace rule says to build after changes.
| name | push-changes |
| description | Push git changes to remote with full workflow including status check, staging, committing, and pushing. Use when the user asks to push changes, push up code, or sync with remote. Includes safety check to prevent pushing directly to main branch. |
Push local changes to the remote repository with safety checks.
Check current branch
git branch --show-current
STOP if on main or master: Warn the user they forgot to create a branch. ALWAYS use the AskQuestion tool:
If the user selects "custom", ask them conversationally for the branch name, then create and switch to it:
git checkout -b <branch-name>
Check status
git status
Review untracked files and modifications.
Stage changes
git add -A
Or selectively add specific files if the user prefers.
Review staged changes
git diff --staged --stat
Commit with descriptive message Analyze the changes and create a commit message following conventional commits format:
git commit -m "$(cat <<'EOF'
<type>(<scope>): <description>
<optional body>
EOF
)"
Types: feat, fix, docs, style, refactor, test, chore
Push to remote
git push -u origin HEAD
Verify push succeeded
git status
Confirm the branch is up to date with remote.
main or master - always create a feature branch first