메뉴
Stage, commit, and push code changes with branch safety and explicit staging. Use when ready to commit work. Invoked by saying "commit", "push", or "commit and push".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Batch-commit all uncommitted changes grouped by relevance. Use when multiple accumulated changes need committing. Invoked by saying "commit all" or "commit everything".
Document completed work — update task log, sync documentation, log observations. Use after finishing a task or batch of changes.
Execute a previously created implementation plan — implement, test, document, and close out. Use when a plan file exists and is ready for implementation.
Merge dev branch into master/main and push. Use when dev changes are ready for production branch. Invoked by saying "merge to master" or "merge to main".
Create a detailed implementation plan before coding. Use when starting a new feature, multi-step refactor, or complex task. Invoked by saying "plan", "create a plan", or "plan this task".
Generate a structured report on completed work, a feature area, or a topic. Saved to the reports directory. Invoked by saying "report", "generate report", or "summarize work".
| name | commit |
| description | Stage, commit, and push code changes with branch safety and explicit staging. Use when ready to commit work. Invoked by saying "commit", "push", or "commit and push". |
Stage, commit, and push only the files you modified in this session to the current working branch.
git branch --show-current.master or main — STOP immediately. Do not stage, commit, or push. Tell the user and wait.dev — you may commit, but do NOT push automatically. After committing, ask: "Committed. Ready to push to dev?" Wait for explicit approval.master or main unless explicitly instructed.Before committing, confirm that ALL required verification steps from the task plan have passed. If any verification is blocked or incomplete, do NOT commit. Report the blocker. See AGENTS.md → Blocker Protocol.
Check git status --short — Review all modified/untracked files. Identify which ones you touched.
Stage only your files — Use git add with explicit file paths. Never use git add -A or git add ..
Write a high-quality commit message using multiple -m flags.
<type>(<optional-scope>): <action-oriented summary>
Allowed Types: feat, fix, refactor, docs, style, data, config, chore, merge
Rules:
-m flags maxFiles: <key files>Updated gateway → feat(gateway): add support for digital wallet paymentsfix stuff → fix(checkout): correct redirect URL for cancelled paymentsPush to the current working branch — If on dev, ask before pushing.
git add . or git add -A.