commit
Git commit workflow. Use this skill whenever the user says "commit", "save changes", "check in", or otherwise wants to commit code. Always use this skill instead of running git commands directly.
What this skill does
# Commit
Create a git commit with a well-crafted conventional commit message.
{% include "_partials/delegate-to-subagent" %}
## Guidelines
- Never commit scratch or temporary files — only intentional source
- Never miss files: all modified source on the branch must be committed
- Create/update `.gitignore` for project-specific scratch patterns
- **Kanban changes ship with code**: if `.kanban/` has modifications, always include them in the same commit. Never leave kanban state unstaged.
## Process
1. **Detect project types** with `code_context` → `detect projects` to pick the right formatters/linters
2. **Format** for each detected type before staging (`cargo fmt`, `go fmt ./...`, `npx prettier --write .`)
3. **Lint** where applicable (`cargo clippy -- -D warnings`)
4. Review `git status` — stage source + tests, skip scratch
5. Commit with a [Conventional Commit](https://www.conventionalcommits.org/en/v1.0.0/#summary) message
6. Report progress
## Examples
**Routine commit:** User says "commit". Detect Rust → `cargo fmt` + `cargo clippy -- -D warnings`. `git status` shows `src/auth/login.rs`, `tests/auth.rs`, untracked `scratch_notes.md`. Skip scratch, stage source + any `.kanban/` changes, commit: `feat(auth): add JWT refresh endpoint`.
**Splitting unrelated work:** `git status` shows a bug fix in `src/parser.rs` and a docs tweak in `README.md`. Commit separately: `fix(parser): handle empty input without panicking`, then `docs: clarify installation steps for macOS`.
## Troubleshooting
### `.kanban/` still shows modifications after committing
Kanban state was written after staging or the stage step missed it. Amend rather than create a follow-up:
```
git add .kanban
git commit --amend --no-edit
```
Use `git add -A` (or `git add . .kanban`) going forward.
### `cargo clippy -- -D warnings` or `cargo fmt --check` fails pre-commit
Fix in place — never commit past failing lints. Don't `#[allow(...)]` to silence:
```
cargo fmt
cargo clippy --fix --allow-staged -- -D warnings
git add -A
```
Re-run `cargo clippy -- -D warnings` to confirm clean.
### `git commit` fails with `pre-commit hook failed` / `husky > pre-commit`
A repo hook (husky, pre-commit, lefthook) rejected the change. Read its output, fix the issue, re-stage, retry. Never use `--no-verify` unless the hook itself is broken.
```
npx prettier --write .
git add -A
git commit -m "<same message>"
```
### Untracked scratch files keep appearing in `git status`
Add ignore patterns and stage `.gitignore` in the same commit if first time:
```
echo 'scratch_*.md' >> .gitignore
echo '*.tmp' >> .gitignore
git add .gitignore
```
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.