How do I install the Ln 003 Push All skill?

Run npx skillmds@latest add majiayu000/ln-003-push-all-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Ln 003 Push All skill do?

Commit and push ALL changes (staged + unstaged + untracked) to the remote repository It is listed under Integrations & APIs on SkillMD.

Is Ln 003 Push All safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ln 003 Push All?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ln 003 Push All free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ln 003 Push All?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ln 003 Push All by majiayu000 — Agent Skill

Name: Ln 003 Push All
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

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

---name: ln-003-push-all-2description: 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 SharedCommits 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 Changes1. Run `git diff --stat` and `git status` to understand ALL changes (staged, unstaged, untracked)2. Identify what was changed and why### Phase 2: Documentation CheckCheck 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 manually3. 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 errors2. If errors remain after 2 fix attempts — report remaining errors to user and proceed### Phase 4: Stage and Commit1. Run `git add -A` to stage everything2. Run `git diff --cached --stat` to show what will be committed3. Run `git log --oneline -3` to match recent commit style4. Compose a concise commit message summarizing ALL changes5. Commit with `Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>`### Phase 5: Push and Report1. Push to the current branch's remote tracking branch2. 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

Frequently asked questions

Ln 003 Push All