cf-commit

# $cf-commit > **CLI Requirement:** NONE — Works without `coding-friend-cli`. See [CLI requirements](../../../docs/cli-requirements.md) for the full matrix. Create a commit for the current changes. Hint: **$ARGUMENTS** ## Workflow ### Step 0: Custom Guide Custom guide — auto-loaded below (if the raw command shows instead of its output, run it yourself): ```! bash "${PLUGIN_ROOT}/lib/load-custom-guide.sh" cf-commit ``` If output is not empty, integrate returned sections: `## Before` → before first step, `## Rules` → apply throughout, `## After` → after final step. ### Step 1: Analyze Changes ```bash bash "${PLUGIN_ROOT}/skills/cf-commit/scripts/analyze-changes.sh" ``` ### Step 2: Identify Conversation-Related Changes Review the current conversation to understand what task was performed and which files were modified as part of that task. - **Prioritize changes from the current conversation** — files you edited or created during this session are the primary candidates for this commit - **Separate unrelated changes** — if `git status` shows files that were NOT part of the current task, do NOT include them - If ALL changes are from the current conversation, proceed normally - If there is a mix, clearly tell the user which files you will stage and which you will skip (and why) ### Step 3: Stage & Scan - Stage only files relevant to the current conversation's task - Do NOT stage unrelated changes from other work - Do NOT stage `.env`, credentials, or secrets - Do NOT u...