commit

Commit Changes

You are tasked with creating git commits for repository changes.

Input

$ARGUMENTS — optional commit message hint, optionally with --baseline <path> (a workflow's run-start snapshot of paths that were already dirty before the run began). Peel the --baseline flag first; the remainder (if any) is the message hint. Empty/literal → infer from history and git diff.

Metadata

node "${SKILL_DIR}/../_shared/git-changes.mjs"
echo "---recent-subjects---"
git log --pretty=%s -n 20 2>/dev/null || true

---recent-subjects--- — up to 20 most recent commit subject lines, used in Step 2 to match the repository's existing commit-message style. Empty on a no-HEAD initial repo.

When --baseline <path> was provided, the Metadata block above was rendered WITHOUT the baseline (render-time substitution cannot capture $ARGUMENTS — same reason code-review's scope helper is LLM-invoked). Before anything else, re-run the snapshot with the baseline threaded and use ITS output as the authoritative ---status--- / ---diffstat--- for the rest of this skill:

node "${SKILL_DIR}/../_shared/git-changes.mjs" --baseline <path>

---pre-existing (do NOT commit — dirty before this run)--- — present in that re-run's output when some listed files were already dirty before the run began. These are out of scope: they are not this run's work. Never git add a path in this section — a workflow commits only the changes it produced. The re-run's ---status--- block already excludes them; they are shown purely so you know they exist and must be left uncommitted.

Context:

• In-session: If there's conversation history, use it to understand what was built/changed
• Standalone: If no context available, rely entirely on git state and file inspection

Process:

1. Check git availability:
   • If in_repo: in the Metadata block is no, tell the user: "This directory is not a git repository. Run git init to initialize one." Stop — do not proceed.