committing-code
Smart Commit
Group changed files logically into focused, atomic commits.
Step 1: Gather State
Run in parallel:
git status --porcelain
git diff --name-status 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.
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
Show git status and list commits created.
More from alexei-led/cc-thingz
using-cloud-cli
Cloud CLI patterns for GCP and AWS. Use when running bq queries, gcloud commands, aws commands, or making decisions about cloud services. Covers BigQuery cost optimization and operational best practices.
2using-modern-cli
>-
2writing-web
>-
2brainstorming-ideas
Brainstorm ideas and stress-test draft plans before coding. Use when user wants to brainstorm, explore approaches, design a feature/API/flow, challenge assumptions, or resolve terminology that blocks the design. NOT for pure decision-tree interviews on a single existing plan ("grill me"); use grill-me. NOT for breaking approved requirements into implementation tasks; use /spec:plan. NOT for general documentation updates; use documenting-code or learning-patterns.
2looking-up-docs
>-
2writing-python
Idiomatic Python 3.12+ development. Use when writing Python code, CLI tools, scripts, or services. Emphasizes stdlib, type hints, uv/ruff/pyright toolchain, and minimal dependencies.
2