auto-commit

A command for checking, committing, and optionally pushing completed code changes through a pull request. A pull request is a proposed change that others can review before it is merged.

In plain words
What is it for?
Creating commits, feature branches, pushed changes, and regular or draft pull requests after development work.
Why use it?
It groups quality checks and version-control steps into one workflow. It also supports safer feature branches instead of putting every change directly on the main branch.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/wigtn/wigtn-plugins/auto-commit
Clone the repo
git clone --depth 1 https://github.com/wigtn/wigtn-plugins
Per session 78 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 7,766 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00078 $0.07766
Opus 5 $0.00039 $0.03883
Sonnet 5 $0.00016 $0.01553
Haiku 4.5 $0.00008 $0.00777

Measured yesterday against content hash 0a174c0c9c8f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

auto-commit scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/wigtn-plugins/commands/auto-commit.md · 479 lines

How it starts

The opening of the file, as written. The whole thing — 479 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Auto Commit

작업 완료 후 변경사항을 분석하고, 품질 검사를 거쳐 피처 브랜치에 커밋하고 PR을 생성합니다.

Pipeline Position

이전 단계 현재 다음 단계
/implement - 구현 완료 /auto-commit - 품질 검사 & PR /review-pr - 동료 리뷰

Usage

/auto-commit                      # 품질 검사 + 브랜치 생성 + PR (기본)
/auto-commit --direct             # main에 직접 커밋 (이전 방식)
/auto-commit --no-push            # 커밋만, 푸시/PR 안함
/auto-commit --no-review          # 품질 검사 스킵 (권장하지 않음)
/auto-commit --message "메시지"   # 수동 메시지 지정
/auto-commit --branch "이름"      # 브랜치명 직접 지정
/auto-commit --no-parallel-review # 순차 리뷰 강제 (병렬 비활성화)
/auto-commit --draft              # Draft PR로 생성

Parameters

  • --direct: main/현재 브랜치에 직접 커밋 (PR 생성 안함, 이전 방식)
  • --no-push: 커밋만 하고 푸시하지 않음
  • --no-review: 품질 검사 스킵 (긴급 핫픽스용)
  • --message: 커밋 메시지 직접 지정
  • --branch: 피처 브랜치명 직접 지정 (기본: 자동 생성)
  • --no-parallel-review: 병렬 리뷰 비활성화, 순차 리뷰 강제
  • --parallel-review: 병렬 리뷰 강제 활성 (자동 조건 미충족 시에도)
  • --draft: Draft PR로 생성 (리뷰 준비 전)

Workflow Mode

  • PR 모드 (기본): 브랜치 판단 → (필요시) 피처 브랜치 생성 → 커밋 → 푸시 → PR 생성/업데이트
  • Direct 모드 (--direct): 현재 브랜치에 직접 커밋 → 푸시 (이전 방식)

Branch Strategy (핵심)

원칙: 브랜치는 "작업 단위(feature/fix)" 당 1개만 생성한다. 무분별한 브랜치 생성을 방지한다.

브랜치 결정 플로우

  1. 현재 피처 브랜치(main/master 아님)에 있음 → 먼저 Stale 검사 (gh pr list --head <branch> --state all):
    • Open PR 존재 → 현재 브랜치 재사용 (커밋 추가 시 PR 자동 갱신)
    • Merged/Closed PR만 존재 → ⚠️ STALE. 재사용 금지 (닫힌 PR에 push해도 다시 열리지 않음). origin/main에서 새 브랜치 분기 후 변경사항 carry-over (Stale Branch Handling 참조)
    • PR 없음 → 현재 브랜치 사용 + 새 PR 생성
  2. main/master에 있음 → 파이프라인 여부 판단:
    • /implement → /auto-commit 파이프라인 (PRD/PLAN 존재) → PRD/PLAN에서 feature name 추출, feat/<feature-name> 브랜치 1개 생성, 해당 feature 커밋을 여기에 누적
    • 단독 호출 → 변경사항이 한 작업 단위면 변경 분석에서 추출한 이름으로 브랜치 1개 생성. 여러 도메인에 걸치면 AskUserQuestion으로 "하나의 PR로 묶을지 / 분리할지" 및 브랜치명 확인

브랜치 재사용 규칙

상황 동작
피처 브랜치 + Open PR 존재 현재 브랜치 재사용 (PR에 커밋 추가)
피처 브랜치 + Merged/Closed PR ⚠️ Stale 처리 — origin/main에서 새 브랜치 분기, 변경사항 carry-over
피처 브랜치 + PR 없음 현재 브랜치 사용, 새 PR 생성
main에서 같은 feature 반복 호출 첫 호출 시 만든 open PR 브랜치 재사용
--branch 옵션으로 명시 해당 이름 사용 (이미 있고 stale이면 새로 분기)
이전 /implement에서 생성된 브랜치 해당 브랜치로 checkout (stale 검사 후)

Read the full file on GitHub · 479 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 479 lines · 78 tokens per session scan A 0a174c0c9c8f

Subscribe to this mod's changes

auto-commit is a command published in the GitHub repository wigtn/wigtn-plugins (45 stars, last pushed 16d ago), licensed Apache-2.0. It adds 78 tokens to every session and 7,766 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.