ln-001-push-all
Commits and pushes all changes (staged, unstaged, untracked) to remote. Use when you need a quick push of everything at once.
What this skill does
> **Paths:** File paths (`references/`, `../ln-*`) are relative to this skill directory. **MANDATORY READ:** Load `references/git_scope_detection.md` — compact git output flags (`--porcelain`, `--oneline -N`, `--stat` first) and pipefail rules. # Push All (Standalone Utility) **Type:** Standalone Utility **Category:** 0XX Shared Commits and pushes ALL current changes (staged, unstaged, untracked) to the remote repository in a single operation. --- ## When to Use This Skill - Quick push of all accumulated changes without manual staging - End-of-session commit when all changes are ready - Any situation where `git add -A && git commit && git push` is the intent --- ## Workflow ``` Analyze → Doc Check → CHANGELOG → Lint Check → Stage → Commit → Push → Report ``` ### Phase 1: Analyze Changes 1. Run `git diff --stat` and `git status` to understand ALL changes (staged, unstaged, untracked) 2. Identify what was changed and why ### Phase 2: Documentation Check Check if related documentation needs updating: | Change Type | Action | |-------------|--------| | Code behavior changed | Update affected docs, comments, examples | | New files/folders added | Update relevant index or list sections | | Config files changed | Check README or setup docs | | No doc impact | Skip | **Skip:** Version bumps (version fields in SKILL.md, README badge) — those are done only on explicit user request. ### Phase 3: CHANGELOG Update If `CHANGELOG.md` exists and changes are significant (not just lint/formatting fixes): 1. Check if today's date already has an entry (`## YYYY-MM-DD`) 2. If yes — append new bullets to existing entry 3. If no — add new `## YYYY-MM-DD` entry (newest first) 4. Write **max 5 bullets**, each starting with `- **Bold label** — description` 5. Only user-visible or architecturally significant changes. Skip: renumbering, internal refactoring, structural fixes, deduplication | Include | Skip | |---------|------| | New capabilities / skills | Renumbering, renaming | | Workflow changes | Internal refactoring (D1-D9 fixes) | | Breaking changes | Deduplication passes | | New integrations | Reference file moves | | Performance improvements users notice | Token efficiency numbers | **Skip if:** no `CHANGELOG.md` in project, or changes are trivial (whitespace, lint auto-fixes only). ### Phase 4: Lint Check **MANDATORY READ:** Load `references/ci_tool_detection.md` (Discovery Hierarchy + Command Registry) Discover and run project linters before committing, per ci_tool_detection.md. **Step 1: Discover linter setup** — first check `docs/project/runbook.md` for explicit lint/format commands (they take priority over auto-detection), then follow ci_tool_detection.md discovery hierarchy. Also check: `CLAUDE.md`, `README.md`, `CONTRIBUTING.md` for lint instructions. **Step 2: Run linters with auto-fix** 1. Run discovered lint commands with `--fix` flag (or equivalent per ci_tool_detection.md Auto-Fix column) 2. If linter reports errors that auto-fix cannot resolve — fix manually 3. If no linter config found in project — skip this phase (log: "No linter configuration found, skipping") **Step 3: Verify** 1. Re-run linters without `--fix` to confirm zero errors 2. If errors remain after 2 fix attempts — report remaining errors to user and proceed ### Phase 5: Stage and Commit 1. Run `git add -A` to stage everything 2. Run `git diff --cached --stat` to show what will be committed 3. Run `git log --oneline -3` to match recent commit style 4. Compose a concise commit message summarizing ALL changes 5. Commit with `Co-Authored-By: Claude Opus 4.6 <[email protected]>` ### Phase 6: Push and Report 1. Push to the current branch's remote tracking branch 2. Report: **branch name**, **commit hash**, **files changed count** --- ## Critical Rules - **Stage everything:** `git add -A` — no partial commits - **Match commit style:** Follow the project's existing commit message convention - **Co-Author tag:** Always include `Co-Authored-By` line - **No version bumps:** Skip version field updates (SKILL.md Version, README badge) unless explicitly requested - **Lint before commit:** Always attempt lint discovery; skip gracefully if no config found --- ## Definition of Done - [ ] All changes staged (untracked + modified) - [ ] Commit created with descriptive message - [ ] Pushed to remote successfully --- **Version:** 1.0.0 **Last Updated:** 2026-02-12
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.