playbooks

home / skills / levnikolaevich / claude-code-skills / ln-003-push-all

ln-003-push-all skill

/ln-003-push-all

This skill commits and pushes all changes (staged, unstaged, untracked) to the remote in one operation, accelerating end-to-end workflow.

npx playbooks add skill levnikolaevich/claude-code-skills --skill ln-003-push-all

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
3.2 KB
---
name: ln-003-push-all
description: "Commit and push ALL changes (staged + unstaged + untracked) to the remote repository"
---

> **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

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 (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**

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 4: 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 5: 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 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

Overview

This skill commits and pushes ALL local changes—staged, unstaged, and untracked—in a single, safe workflow. It runs project-aware checks (documentation and linters), stages everything, creates a concise commit that follows the repo style, includes the required Co-Author footer, and pushes to the current remote branch. The goal is a fast, predictable end-of-session push that respects project conventions and flags unresolved lint issues before commit.

How this skill works

The skill inspects the working tree with git status and git diff --stat to list all changes, then runs a documentation check and attempts to discover and run configured linters with auto-fix. After lint verification it stages all files with git add -A, shows the staged diff, composes a concise commit message consistent with recent commits, adds the Co-Authored-By line, and pushes to the branch's remote tracking branch. It reports branch name, commit hash, and files-changed count after push.

When to use it

  • You want to quickly push all accumulated edits at the end of a work session.
  • You intend to perform git add -A && git commit && git push in one automated step.
  • You need to ensure linters run (with auto-fix) before committing everything.
  • You added new files or folders and want them included without manual staging.
  • You prefer a single, auditable commit that summarizes all ongoing changes.

Best practices

  • Run the workflow only when changes are cohesive; avoid combining unrelated work in one commit.
  • Review git diff --stat and git status output from the Analyze phase before proceeding.
  • Follow the project's existing commit message style by referencing recent oneline commits.
  • Allow linters to run with auto-fix and fix any remaining errors manually if required.
  • Do not perform implicit version bumps or CHANGELOG edits unless explicitly requested.

Example use cases

  • End-of-day snapshot: commit and push all local work before switching machines.
  • Rapid push after bulk edits like formatting, refactors, or adding new examples.
  • When onboarding and you want to push a set of initial files and configs at once.
  • Emergency follow-up: include hotfix files, tests, and docs in a single commit.
  • CI prep: run linters and push a clean working tree before creating a PR.

FAQ

What happens if the linter finds errors it cannot auto-fix?

The skill reports remaining lint errors after two fix attempts and pauses for manual resolution; it will still proceed if you explicitly choose to continue, but reporting ensures you know what to fix.

Will this skill change version files or the changelog automatically?

No. Version bumps and changelog updates are skipped unless you explicitly request them.