with one click
commit-and-push
// Commit code changes and push via Git. Use when the user asks to commit, push, or save their work to the repository.
// Commit code changes and push via Git. Use when the user asks to commit, push, or save their work to the repository.
Capture the four RakuRaku showcase screenshots on a connected device and refresh the fastlane metadata. Use when the user asks to take, update, or regenerate screenshots.
Release engineering tasks for RakuRaku IME — version bumping, building release APKs, tagging, and creating GitHub releases. Use when the user asks to prepare a release, bump version, tag, or build for distribution.
Review code for quality, correctness, and security vulnerabilities. Use when the user asks to review code, audit for security issues, or check for bugs and anti-patterns.
Writing/updating project documentation for RakuRaku IME (README, TODOs, LICENSE notices, AI-assistant guide files). Use when the user asks to update docs or rewrite user-facing text.
| name | commit-and-push |
| description | Commit code changes and push via Git. Use when the user asks to commit, push, or save their work to the repository. |
| argument-hint | commit message or description of changes |
You are committing and pushing code changes for RakuRaku IME (輕鬆輸入法).
The project's history is mixed — some commits use a conventional-style prefix (docs:, perf:, fix:), others use a plain imperative subject (Add …, Fix …, Update …, Remove …, Implement …). When in doubt, match the style of nearby recent commits (git log --oneline -20).
ccdaf29.Signed-off-by or Co-Authored-By trailers. Do not add them unless the user explicitly asks.Add … — new feature or file.Fix … — bug fix.Update … — dependency or content update.Remove … — deletion of code or files.Implement … — larger new capability.docs: …, perf: …, fix: … — conventional-prefix variants used in recent commits.git status and git diff to understand what will be committed.git add -A. Do not stage:
local.properties, signing keys).app/build/, .gradle/, .idea/ where gitignored).git commit -m "$(cat <<'EOF'
Subject line here
Optional body explaining why.
EOF
)"
origin/main immediately after the commits land.
Do not pause to ask for confirmation first; the user's standing
preference for this repo is "just push". Still refuse a force-push
to main unless explicitly requested.origin → git@github.com:hiroshiyui/RakuRakuIME.git.main.main without explicit user approval.