Should I always push all changes together?

Yes. This skill is designed to avoid partial commits by staging everything before committing and pushing.

What if there is no linter configuration?

Proceed by skipping the lint phase and continue with staging, committing, and pushing; log should note 'No linter configuration found, skipping'.

How are version bumps handled?

Version bumps should be skipped unless explicitly requested; this skill focuses on including all changes in a single push without automated version updates.

ln-003-push-all

Scanned

npx machina-cli add skill levnikolaevich/claude-code-skills/ln-003-push-all --openclaw

Files (1)

SKILL.md

3.2 KB

Paths: File paths (shared/, references/, ../ln-*) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.

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 → Lint Check → Stage → Commit → Push → Report

Phase 1: Analyze Changes

Run git diff --stat and git status to understand ALL changes (staged, unstaged, untracked)
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 (CHANGELOG, version fields) — those are done only on explicit user request.

Phase 3: Lint Check

MANDATORY READ: shared/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 per ci_tool_detection.md discovery hierarchy. Also check: CLAUDE.md, README.md, CONTRIBUTING.md for lint instructions.

Step 2: Run linters with auto-fix

Run discovered lint commands with --fix flag (or equivalent per ci_tool_detection.md Auto-Fix column)
If linter reports errors that auto-fix cannot resolve — fix manually
If no linter config found in project — skip this phase (log: "No linter configuration found, skipping") Step 3: Verify
Re-run linters without --fix to confirm zero errors
If errors remain after 2 fix attempts — report remaining errors to user and proceed

Phase 4: Stage and Commit

Run git add -A to stage everything
Run git diff --cached --stat to show what will be committed
Run git log --oneline -3 to match recent commit style
Compose a concise commit message summarizing ALL changes
Commit with Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Phase 5: Push and Report

Push to the current branch's remote tracking branch
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 CHANGELOG/version updates unless explicitly requested
Lint before commit: Always attempt lint discovery; skip gracefully if no config found

Version: 1.0.0 Last Updated: 2026-02-12

Source

git clone https://github.com/levnikolaevich/claude-code-skills/blob/master/ln-003-push-all/SKILL.mdView on GitHub

Overview

This skill commits and pushes ALL current changes—staged, unstaged, and untracked—to the remote in a single operation. It’s ideal for quick, comprehensive pushes at session end or whenever you want a single, complete update to share.

How This Skill Works

The process analyzes changes with git diff --stat and git status, runs project lint checks via the discovery workflow, then stages everything with git add -A, composes a concise, style-consistent commit message (including Co-Authored-By), and pushes to the current branch’s remote tracking branch.

When to Use It

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
Preparing to share a feature branch with all local edits including untracked files
Enforcing a single, comprehensive commit that includes a Co-Authored-By line

Quick Start

Step 1: Analyze changes with git diff --stat and git status, then assess what changed
Step 2: Run lint discovery per ci_tool_detection.md, apply auto-fix, and verify no errors (or skip if no config)
Step 3: Stage all changes (git add -A), commit with a concise message (including Co-Authored-By), and push to the remote

Best Practices

Stage everything: use git add -A to avoid partial commits
Follow the project's commit message conventions for consistency
Include a Co-Authored-By line when collaborating (e.g., Co-Authored-By: Name <email>)
Skip version bumps unless explicitly requested by the user
Lint before commit: run discovery and auto-fix, then verify zero errors

Example Use Cases

After finishing a feature with code changes, docs updates, and new files, push all in one commit
End-of-day session: commit everything (including untracked files) and push to the remote
Refactoring that touches multiple modules and untracked helper files, pushed together
Collaborative bug fix where teammates rely on a Co-Authored-By attribution
Module update that changes config, tests, and code, pushed as a single update

Frequently Asked Questions

Add this skill to your agents