Automated summary
This command commits and pushes current changes as an intermediate checkpoint, without closing the associated issue.
Strengths
- Quickly saves work in progress without disrupting flow
- Includes a light review to catch obvious issues
- Automatically includes issue number and Claude Code signature in commit message
- Automatically reports progress on the GitHub issue
Limitations
- Does not create a pull request or close the issue
- Quality review is more superficial than /commit/merge
- Requires branch name to contain a valid issue number
Use this command when you want to save your progress mid-task without finalizing.
Do not use it to finish a task; prefer /commit/merge or /issue/finish to close the issue.
Security analysis
CautionThe skill uses git and gh commands to commit and push changes; these are powerful but used for legitimate version control purposes. No destructive or exfiltrating actions detected.
No concerns found
How this analysis is madeExamples
/commit/pushI've completed the initial implementation but haven't tested everything yet. Save my work.description: Commit and push changes (途中保存)
Commit & Push（途中保存）
変更をコミット＆プッシュ（途中保存、Issueは開いたまま）
重要:
- このコマンドは途中保存用です
- Issueはクローズしません
- Worktreeは削除しません
- タスク完了時は
/issue/finishまたは/commit/mergeを使用
vs /commit/merge
| 特徴 | /commit/push | /commit/merge | |------|-------------|---------------| | 目的 | 途中保存 | タスク完了 | | レビュー | 簡易 | 品質チェック | | PR作成 | ❌ なし | ✅ 作成 | | マージ | ❌ なし | ✅ squash merge | | Issueクローズ | ❌ しない | ✅ する | | Worktree削除 | ❌ しない | ✅ する |
Workflow
Phase 0: 簡易レビュー
Step 0: QA回答の確認
コミット前に未確認のQA回答がないか確認：
# docs/qa/answers.jsonl をチェック
if [ -f "docs/qa/questions.jsonl" ]; then
echo "QA回答を確認中..."
fi
新しい回答がある場合：
- 回答内容を表示
- 仮決定と異なる場合は、変更が必要か確認
- 必要に応じて実装を修正してからコミット
Step 1: 変更内容を確認
git status
git diff --stat
-
簡易品質チェック 以下の観点で変更をチェック：
- ✓ 明らかな問題: 未完成のコード、デバッグ用コード、コメントアウトされたコード
- ✓ セキュリティ: 機密情報の混入（API key、password等）
- ✓ データ保護: 重要データが
data/local/ではなくdata/shared/に保存される設計か - ✓ ハードコーディング: 明らかなマジックナンバーや固定パスがないか
- ✓ テスト: テストの追加が必要な変更がないか
-
問題があれば指摘
- 重大な問題: コミット前に修正を提案
- 軽微な問題: 注意点として報告しつつコミット続行
Phase 1: Commit & Push
-
すべての変更をステージング
git add . -
コミット
- Conventional Commits 形式を使用
- Issue番号を含める（
Refs #ISSUE_ID） - Claude Code署名を含める
-
プッシュ
git push -u origin $(git branch --show-current)
Phase 2: 進捗報告
- Issueに進捗報告
- コミットハッシュ
- 変更ファイル数
- 次のステップ
Implementation
現在のブランチから Issue 番号を取得：
BRANCH=$(git branch --show-current)
ISSUE_ID=$(echo "$BRANCH" | grep -oE '[0-9]+' | head -1)
# エラーチェック
if [ -z "$ISSUE_ID" ]; then
echo "Error: Could not extract Issue ID from branch name: $BRANCH"
echo "Branch name must contain Issue number (e.g., feature/123-description)"
exit 1
fi
変更をステージング＆コミット：
git add .
git commit -m "適切なコミットメッセージ
Refs #${ISSUE_ID}
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>"
プッシュ：
git push -u origin $(git branch --show-current)
Issueに報告：
gh issue comment "$ISSUE_ID" --body "## コミット完了（途中保存）
- コミット: [hash]
- 変更: [files]
- 次のステップ: [...]
---
*Issueは開いたままです。タスク完了時は `/issue/finish` を実行してください。*"
Output
- 簡易レビュー結果（問題があれば）
- コミットハッシュ
- 変更ファイル数
- Issue コメント URL
- 次のステップの案内
Note
このコマンドは途中保存用です。
タスクが完了したら /issue/finish を実行してください。
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/commit-push-intermittent-save-mrwaka6t/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/commit-push-intermittent-save-mrwaka6t' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/commit-push-intermittent-save-mrwaka6t/download' --output '.skill-downloads/commit-push-intermittent-save-mrwaka6t/SKILL.md.part' && mv '.skill-downloads/commit-push-intermittent-save-mrwaka6t/SKILL.md.part' '.skill-downloads/commit-push-intermittent-save-mrwaka6t/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/commit-push-intermittent-save-mrwaka6t/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.