alexei-led/committing-code

<!-- generated by scripts/build/generate-skills.py — edits to this file will be overwritten by `make build`. Edit the canonical SKILL.md (or add a SKILL.codex.md / SKILL.pi.md sidecar to diverge). --> <!-- Platform guidance for non-Claude models (Codex CLI, Gemini CLI) --> <!-- Persistence: Keep going until the task is fully resolved. Do not stop at the first obstacle. --> <!-- Tool use: Use available tools to verify — do not guess at file contents, paths, or command output. --> <!-- Planning: Reflect between steps. Decompose complex problems into logical sub-steps before acting. --> <!-- Reliability: Assess risk before irreversible actions. Ask for clarification on ambiguity. --> <!-- Completeness: Generate complete responses without truncating. Review your output against the original constraints. -->

Smart Commit

Group changed files logically into focused, atomic commits.

Scope: only inspect changes, group them, and create normal commits. Do not rewrite history, amend existing commits, force-push, or stage secrets. Include relevant git status, git diff, and git log output in the proposal.

Any commit plan must explicitly say the first inspection commands are git status --short, git diff --stat HEAD, git diff HEAD, and git log --oneline -8. Any commit summary must include a final git status --short plus recent git log --oneline -n <created> output.

Step 1: Gather State

Run in parallel before any commit:

git status --short
git diff --stat HEAD
git diff HEAD
git log --oneline -8

If no changes: Say "Nothing to commit" → stop.

Step 2: Analyze & Present

Group files by: feature (impl+tests), fix (bug+test), refactor, docs, config

Match commit style from recent history.

Present proposed commits:

Proposed commits:

1. feat: add user validation
   - src/validate.ts
   - src/validate_test.ts

2. docs: update README
   - README.md

Step 3: Execute

Never stage files matching .env, *.pem, *credentials*, or *secret*. Flag to user if detected in changes. Safe source/test files may still be grouped and committed separately after approval.

For each group, run git add + commit.

User will be prompted to approve each write operation (git add/commit not pre-allowed).

Step 4: Summary

Run final checks and show the result:

git status --short
git log --oneline -n <number-of-created-commits>

Summarize commits created and any remaining uncommitted files.

---