SCE Commit

Execution contract

Own this workflow from input through its terminal user-visible response. Follow its steps, gates, and stops in order; do not add, skip, reorder, or merge them. Keep intermediate workflow state private and continue immediately until a defined wait or stop. Resume user waits in this same skill and session. Render user-visible output only from the named workflow layouts or reports. Do not expose raw internal state or add text around a rendered layout or report. Non-SCE helpers may assist, but must return to the active step without changing workflow order, gates, waits, writes, validation, stops, or terminal output. Do not invoke another SCE skill, package, or workflow command.

Phase reference

Both paths below dispatch to the same phase, whose steps and boundaries live in references/atomic-commit.md. This document holds the control flow — which path runs, what the phase receives, and how its result branches — and the reference holds the phase itself.

Read references/atomic-commit.md before running the phase, not after. A regular run that stops at the staging gate, and a bypass run that finds nothing staged, both end without ever needing it.

Input

invocation input is optional. Split it into two parts before invoking the skill:

[mode-token] [commit context]

• mode-token is present only when the first whitespace-separated token is exactly oneshot or skip, compared case-insensitively. Any other first token is not a mode token.
• commit context is everything else: free-form prose that refines message wording only.

A mode-token selects the bypass path. Its absence selects the regular path. Do not infer the bypass path from anything else — not from the commit context, not from repository state, and not from the conversation.

Empty invocation input is valid. It selects the regular path with no commit context, and commit intent is inferred from the staged changes alone.

Pass commit context to the Atomic commit phase unmodified. Do not restate, summarize, or pre-scope it. Never pass the mode-token as commit context.

Staged changes are the source of truth for what is being committed. This command never stages, unstages, or modifies files.

For example: $sce-commit oneshot.

Workflow

Follow exactly one path.

Regular path (no mode token)

1. Confirm staging

Before running the phase, stop and prompt the user with the Regular-mode staging gate layout from references/output.md.

Wait for the user's confirmation. Do not stage files on their behalf, and do not skip this prompt because the working tree looks ready.

2. Propose commits

After confirmation, read references/atomic-commit.md, then run the Atomic commit phase with mode: regular and the commit context.

Do not write commit messages yourself.

Branch on status:

blocked -> Render the Blocked layout from references/output.md. Stop.

proposal -> Render the Regular proposal layout from references/output.md, which covers each proposed commit's message and files, and the split rationale when more than one commit is proposed.

Then stop. The regular path is proposal-only.

Do not run git commit. Do not offer to commit on the user's behalf. The user runs the commits they accept.

Bypass path (oneshot or skip)

1. Validate that staged content exists

Run git diff --cached --quiet. A zero exit status means nothing is staged.

When nothing is staged, stop with the No staged changes layout from references/output.md.

Do not stage anything. Do not proceed to the phase.

2. Request one commit message

Read references/atomic-commit.md, then run the Atomic commit phase with mode: bypass and the commit context.

Bypass mode is the phase's contract for producing exactly one message. Do not restate its overrides here; the Atomic commit phase owns them.

Branch on status:

blocked -> Render the Blocked layout from references/output.md and stop. Do not commit.

bypass_message -> Continue to the next step.

The phase never returns proposal in bypass mode. Treat a proposal result as a contract violation: report it and stop without committing.

3. Execute exactly one commit

Follow the Bypass execution handoff in references/atomic-commit.md exactly as written. That handoff is the sole owner of the execution sequence; do not reconstruct, supplement, or restate it here.

On success, render the Bypass success layout from references/output.md and stop.

On failure, render the Bypass Git failure layout from the same file and stop.

The handoff owns commit-failure handling. This workflow owns only the matching user-visible result layout above.

Rules

• Produce at most one commit per invocation, and only on the bypass path.
• Never commit on the regular path.
• Recognize oneshot and skip only as an exact case-insensitive first token. They are behaviorally identical.
• Read references/atomic-commit.md before running the phase.
• Do not duplicate the internal instructions of the Atomic commit phase.
• Do not stage, unstage, restore, or otherwise modify repository or worktree files. The bypass commit-message temp file is the sole exception: it must live outside the working tree, so it is not a repository or worktree file.
• Do not amend, reset, revert, rebase, or push.
• Do not read unstaged or untracked changes as commit input.
• Do not infer success when the Atomic commit phase returns a non-success status.
• Do not proceed past a failed git commit.
• Do not run plan, task, or validation workflows from this command.