Atomic Commit
Atomic Commit helps create clean, atomic commits by analyzing changes, detecting mixed concerns, and ensuring each commit is a complete unit of work. Key words to detect are atomic, atomic commits, clean commits.
What this skill does
# Atomic Commit Standalone skill for non-TDD workflows. Helps create clean, atomic commits by analyzing changes and detecting mixed concerns. ## Atomic Commit Definition - Does exactly one thing (one feature/fix/refactor) - Leaves codebase in working state (builds and tests pass) - Can be reverted independently - Doesn't mix unrelated concerns ## Workflow ### 1. Analyze Changes ```bash git status && git diff && git diff --staged ``` ### 2. Detect Mixed Concerns Look for files mixing: - Multiple features - Bug fixes + features - Refactoring + new functionality - Multiple unrelated bug fixes - Code + documentation (unless for same feature) - Tests for multiple features ### 3. Group Commits Group files by shared purpose. Present grouping to user for confirmation. Example: ``` Group 1: "Add user auth" → auth/login.ts, auth/session.ts, tests/auth/login.test.ts Group 2: "Fix password validation" → validators/password.ts, tests/validators/password.test.ts ``` ### 4. Create Each Commit For each group: 1. Stage: `git add <file1> <file2>` (NO `git add .`) 2. Review: `git diff --staged` 3. Test: Run tests, ensure pass 4. Build: Run build if applicable, ensure success 5. Commit: Use conventional commit format 6. Verify: `git log -1 --oneline` Conventional commit types: `feat|fix|refactor|docs|test|chore|perf|style` ### 5. Final Check ```bash git log --oneline -n <N> ``` ## Issue Integration - Check user message or branch name for issue number - IF no issue: ask if user wants to create one - IF user does not want to provider, leave it blank - IF yes: help write description, offer `gh issue create` or `glab issue create` - Include in commits: `"feat: description (#42)"` ## Guidelines **DO:** One logical change, include related tests, run tests, clear messages, issue numbers **DON'T:** Mix features/fixes/refactors, commit broken code, vague messages, debug code ## TODO Pattern ☐ Analyze: git status/diff ☐ Identify file purposes ☐ Detect mixed concerns ☐ Group into atomic commits ☐ Confirm with user ☐ For each: stage → review → test → build → commit → verify ☐ Final review ## Activation Use when user says: "atomic", "clean commits", "break down commits", "split commits" DO NOT use for TDD workflows (use TDG skill). ## Closing "Created N atomic commits. Tests pass. Would you like to review history, push, or create PR?"
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.