メニュー
Stage, commit, and push uncommitted code with a well-structured conventional commit message. Use when the user asks to push code, commit and push, save changes to remote, or sync local changes with GitHub.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | push-code |
| description | Stage, commit, and push uncommitted code with a well-structured conventional commit message. Use when the user asks to push code, commit and push, save changes to remote, or sync local changes with GitHub. |
Stage all changes, generate a conventional commit message, and push to the remote branch.
gh auth status)CURRENT_BRANCH=$(git branch --show-current)
If $CURRENT_BRANCH is main, master, dev, develop, production, or matches release/*:
git checkout -b <type>/<short-description>.<branch> to keep <protected> safe."git status
git diff --stat
.env, *.jks, credentials) are staged../gradlew ktlintCheck # Lint
./gradlew test # Unit tests
./gradlew build # Full build
If any check fails, report the errors and stop.
Use the conventional commit format:
<type>(<scope>): <subject>
<body>
<footer>
Types: feat, fix, refactor, docs, style, test, chore, perf
Subject: imperative mood, max 50 chars, no trailing period.
Body: explain WHAT changed and WHY. List modified files/modules. Document breaking changes.
Footer: Closes #<issue> if applicable.
Never add Co-Authored-By: trailers or "Generated with …" lines. The footer contains only Closes #<issue> when applicable.
Example:
feat(websocket): implement Binance WebSocket connection for crypto prices
- Added WebSocketManager class with retry logic and exponential backoff
- Created CryptoPriceModel data class for price updates
- Configured connection for BTC, ETH, and top 50 coins
Closes #12
git add .
git commit -m "<generated-message>"
CURRENT_BRANCH=$(git branch --show-current)
Double-check the branch is NOT protected. Then push:
git push origin "$CURRENT_BRANCH"
main, master, dev, develop, production, or release/* — even if the user asks.Turn app screenshots into a cinematic product video — a self-contained animated HTML showcase and an exported MP4. Use when the user has app screenshots (or the raw captures from deploy-ss) and wants a "product video", "promo video", "sizzle reel", "app trailer", "launch video", or a shareable motion showcase / App Store preview. Companion to deploy-ss (which makes the static store screenshots).
Generate App Store and Play Store deployment assets — iPhone screenshots, iPad screenshots, and a Play Store feature graphic — from raw app UI screenshots. Use this skill whenever the user has app screenshots and wants to publish to the App Store or Google Play, mentions "store screenshots", "marketing screenshots", "feature graphic", "app store assets", "App Store Connect", "Play Console", "Google Play listing", or asks how to prepare their app's listing for submission. Trigger this even when the user just uploads phone screenshots and says something vague like "make these look good for the store" or "I'm submitting my app, help me with the visuals" — those are still this skill.
Generate App Store and Play Store deployment assets — iPhone screenshots, iPad screenshots, and a Play Store feature graphic — from raw app UI screenshots. Use this skill whenever the user has app screenshots and wants to publish to the App Store or Google Play, mentions "store screenshots", "marketing screenshots", "feature graphic", "app store assets", "App Store Connect", "Play Console", "Google Play listing", or asks how to prepare their app's listing for submission. Trigger this even when the user just uploads phone screenshots and says something vague like "make these look good for the store" or "I'm submitting my app, help me with the visuals" — those are still this skill.
Create a GitHub Pull Request to merge the current branch into main with a well-structured title and description using GitHub CLI. Use when the user asks to create a PR, open a pull request, submit a merge request, or send changes for review.
Merge an approved GitHub Pull Request after validating CI checks, review status, and mergeability. Use when the user asks to merge a PR, complete a pull request, or land a branch.
Run the full push, create PR, review pipeline in sequence: stage/commit/push (push-code), create a PR into main (create-pr), then approve or request changes on that PR (review-pr). Use when the user says pcr, push commit review, push and create pr and review, or wants one workflow from local changes to an opened and reviewed pull request.