local-git

Inspect local git status and diffs, commit changes, and manage isolated worktrees.

33|1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/infinition/LaRuche --skill local-git-infinition
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: local-git
Source: https://github.com/infinition/LaRuche/tree/main/laruche/skills/local-git
Command: npx skills add https://github.com/infinition/LaRuche --skill local-git-infinition

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Recording local git history safely is error-prone: careless staging sweeps in secrets or build artifacts, commits land on the wrong branch, and risky experiments pollute the main checkout. This Skill enforces a disciplined inspect-then-commit workflow and provides isolated worktrees for speculative work. ## Core Features & Use Cases - State Inspection: Use git_status, git_diff (staged or unstaged), and git_log to see exactly what changed and what will be recorded before committing. - Disciplined Committing: Follow a staged-diff-first workflow that produces why-focused commit messages matching the repository's existing style, while avoiding the add_all trap that sweeps in secrets and large files. - Isolated Worktrees: Use git_worktree_enter and git_worktree_exit to run risky refactors or dependency upgrades in a separate worktree without touching the main checkout. - Use Case: Before committing a bug fix, run git_status, read the staged diff, write an imperative message explaining why, then confirm with git_log that the commit landed as intended. ## Quick Start Show me the current git status and staged diff, then commit my changes with a message explaining why the fix was needed.

Frequently Asked Questions about local-git

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely commit changes in git without staging unwanted files?▼

Run git_status first to see modified, staged, and untracked files, then read the staged diff with git_diff before committing. Avoid add_all unless you have verified the untracked list, since it stages everything not ignored, including secrets and build artifacts.

What is the difference between staged and unstaged git diff?▼

git_diff without the staged flag shows unstaged changes, while the staged flag shows exactly what will be recorded in the next commit. Always read the staged diff before committing, since it is the only way to know what you are actually recording.

How do I write a good git commit message?▼

Read git_log first to match the repository's existing style, then write a first line under about 72 characters in imperative mood that says why, not what. Add a blank line and reasoning if the motivation is not obvious from the diff.

When should I use a git worktree instead of a branch?▼

Use a worktree for speculative or risky work you may discard entirely, such as large refactors or dependency upgrades. git_worktree_enter creates an isolated copy so the main checkout stays untouched, but commit before exiting since uncommitted worktree changes are easy to lose.

Why does git commit report nothing to commit?▼

Nothing is staged, either because edits went to a different path than expected or add_all was omitted. Run git_status to see where the changes actually are, and check whether the session is inside a worktree rather than the original repository.