# Ask Before Push

> Use when work is complete and git actions may follow. Ask before any git commit or git push unless the user explicitly instructs commit and/or push in the current request.

- Skill: `kim-dh2417/ask-before-push` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add kim-dh2417/ask-before-push`
- Raw SKILL.md: https://api.skillmd.com/api/skills/kim-dh2417/ask-before-push/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: kim-dh2417 (https://skillmd.com/u/kim-dh2417)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/kim-dh2417/ask-before-push

---


# Ask Before Push

## Overview

Use this skill when implementation, documentation, or review work is done and the next likely step is `git commit` or `git push`.

The purpose of this skill is to prevent unsolicited git history changes. The assistant must ask the user before:

- creating a commit
- pushing to any remote
- doing both in one sequence

Exception:

- If the user explicitly asks for commit or push in the current request, treat that as approval and perform the requested git actions.
- Examples of explicit approval:
  - `커밋해줘`
  - `푸시해줘`
  - `커밋 푸시 해줘`
  - `commit and push`

## Workflow

1. Finish the requested work first.
2. Check the repository state.
3. Summarize the meaningful changes for the user in concise plain language.
4. If the user has not explicitly requested git actions, ask whether to:
   - commit only
   - commit and push
   - leave changes uncommitted
5. Wait for the user's answer before running any `git add`, `git commit`, or `git push`.
6. If the user explicitly requested commit or push, skip the question and execute only the approved actions.

## Required Behavior

- Never create a commit unless the user explicitly approves it.
- Never push unless the user explicitly approves it.
- Do not assume that prior approval for one task applies to later tasks.
- If the user asks only for implementation, stop after reporting completion and verification results.
- If the user previously asked for commit or push in the same thread, that instruction is sufficient only for that specific request.
- When the user says `커밋 푸시 해줘` or an equivalent explicit instruction, do not ask again; proceed with commit and push.

## Message Pattern

When work is complete and git actions are possible but not yet approved, use this pattern:

- brief outcome summary
- brief verification summary
- short question asking whether to commit and/or push

Example:

`변경 적용과 검증이 끝났습니다. build/lint도 통과했습니다. 이 변경을 커밋하고 원격에 푸시할까요?`

When git actions are already explicitly approved, use this pattern:

- brief outcome summary
- brief verification summary
- execute commit and/or push
- report the commit hash and push result

## Scope Notes

- This skill is about permission and workflow, not commit message generation.
- If the user approves a commit but does not provide a message, propose a short, concrete commit message.
- If the user approves push, confirm the target branch when it is unclear.
- The phrase `커밋 푸시 해줘` counts as direct approval for both commit and push.