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.
Best use case
ln-001-push-all is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Commits and pushes all changes (staged, unstaged, untracked) to remote. Use when you need a quick push of everything at once.
Teams using ln-001-push-all should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ln-001-push-all/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ln-001-push-all Compares
| Feature / Agent | ln-001-push-all | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Commits and pushes all changes (staged, unstaged, untracked) to remote. Use when you need a quick push of everything at once.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
> **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. If `shared/` is missing, fetch files via WebFetch from `https://raw.githubusercontent.com/levnikolaevich/claude-code-skills/master/skills/{path}`.
# 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:** `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** — 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 <noreply@anthropic.com>`
### 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-12Related Skills
ln-914-community-responder
Responds to unanswered GitHub discussions and issues with codebase-informed replies. Use when clearing community question backlog.
ln-913-community-debater
Launches RFC and debate discussions on GitHub. Use when proposing changes that need community input or voting.
ln-912-community-announcer
Composes and publishes announcements to GitHub Discussions. Use when sharing releases, updates, or news with the community.
ln-911-github-triager
Produces prioritized triage report from open GitHub issues, PRs, and discussions. Use when reviewing community backlog.
ln-910-community-engagement
Analyzes community health and delegates engagement tasks. Use when managing GitHub issues, discussions, and announcements.
ln-840-benchmark-compare
Runs built-in vs hex-line benchmark with scenario manifests, activation checks, and diff-based correctness. Use when measuring hex-line MCP performance against built-in tools.
ln-832-bundle-optimizer
Reduces JS/TS bundle size via tree-shaking, code splitting, and unused dependency removal. Use when optimizing frontend bundle size.
ln-831-oss-replacer
Replaces custom modules with OSS packages using atomic keep/discard testing. Use when migrating custom code to established libraries.
ln-830-code-modernization-coordinator
Modernizes codebase via OSS replacement and bundle optimization. Use when acting on audit findings to reduce custom code.
ln-823-pip-upgrader
Upgrades Python pip/poetry/pipenv dependencies with breaking change handling. Use when updating Python dependencies.
ln-822-nuget-upgrader
Upgrades .NET NuGet packages with breaking change handling. Use when updating .NET dependencies.
ln-821-npm-upgrader
Upgrades npm/yarn/pnpm dependencies with breaking change handling. Use when updating JavaScript/TypeScript dependencies.