cf-commitlisted

# $cf-commit Create a commit for the current changes. Hint: **$ARGUMENTS** ## Workflow ### Step 0: Custom Guide ```! bash "${PLUGIN_ROOT}/lib/load-custom-guide.sh" cf-commit ``` If the block above printed anything, apply only the `## Before`, `## Rules`, and `## After` sections; if it shows the raw command instead of output, re-run that exact `load-custom-guide.sh` fence now. ### 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 use `git add .` or `git add -A` **Secret scan** — after staging, check for accidental secrets: ```bash bash "${PLUGIN_ROOT}/skills/cf-commit/scripts/scan-secrets.sh" ``` The script prints `SE