commit

<arc_runtime> Requires the full Arc bundle. Arc-owned paths (agents/, references/, disciplines/, templates/, scripts/, rules/, skills/) resolve from the plugin root — the directory containing agents/ and skills/. Everything else is the user's repository. </arc_runtime>

<rules_context> Load before committing:

• rules/git.md — commit-message, husky, and lint-staged conventions this skill must respect. Its Hooks section describes repo setup (audit/launch territory), not a commit-time obligation — an unsatisfied MUST there is a note, not a task.
• references/diff-review-checklist.md — apply during the pre-commit review step (step 1).

</rules_context>

Commit Changes

Commit, push, and publish changes, intelligently splitting into separate commits when changes span multiple domains.

Usage:

• /arc:commit - Auto-analyze and commit (may create multiple commits)
• /arc:commit push - Commit, push, then publish changed npm packages if present
• /arc:commit publish - Alias for the push-and-publish path

On the push/publish path, /arc:commit publishes a package whose version is already committed and not yet on the registry. /arc:release owns bumping versions, changelogs, and coordinated multi-package releases. Route version bumps there instead of doing them here.

The canonical order across both skills is commit → push → publish → tag.

Read the user's invocation: no argument means commit only; "push" or "publish" both mean the push-and-publish path.

Inspect Current Git State

Run these commands first and read the output before deciding on a commit strategy:

git status --porcelain 2>/dev/null || echo "(no changes)"
git diff --stat 2>/dev/null | head -20 || echo "(no diff)"
git log --oneline -5 2>/dev/null || echo "(no commits)"   # style reference

git status --porcelain is the authoritative file list (the stat is a preview, and it truncates); read the contents of untracked files before judging them stray.

If there are no changes, tell the user and stop.