aspiers/ai-config / .agents/skills/git-staging
git-staging
VerifiedStage whole files, selected hunks, or selected lines in Git without interactive prompts. Use when preparing an exact commit boundary while preserving unrelated working-tree changes.
Non-interactive Git Staging
Stage only the changes intended for the next commit. The index is shared state: preserve anything already staged unless the user explicitly asks to replace or unstage it.
Workflow
-
Inspect all three states:
git status --short git diff --no-ext-diff git diff --cached --no-ext-diff -
Derive the desired commit boundary from the user's request and the diff. Group by logical purpose rather than file count.
-
Choose the least complex safe operation:
- complete file:
git add -- <path>; - part of a file: construct a patch and apply it to the index;
- ambiguous overlap with existing staged work: stop and clarify.
- complete file:
-
Verify both sides of the boundary:
git diff --cached --no-ext-diff git diff --no-ext-diff git status --short
A successful git add or git apply is not sufficient evidence; the staged
diff must contain the intended change and exclude unrelated work.
Partial staging
For selected hunks or lines, read
Partial staging with index patches before
constructing the patch. It contains the patch rules, validation sequence, and
failure recovery. Do not use interactive git add -p in a non-interactive
agent session.
Safety
- Use
--before paths that could be parsed as options. - Do not discard working-tree content as part of staging.
- Do not use broad commands such as
git add .when unrelated changes are present or the requested boundary is narrower. - Keep temporary patches in a repository-approved ignored location and remove them when no longer needed.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 465k | Updated | Claude CodeCodex | Verified | Install |
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 465k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |