Skip to content
cccskills
FreePublished on GitHub

git-staging

Stage 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.

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

  • SKILL.md1.8 KB
  • references/partial-staging.md1.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

  1. Inspect all three states:

    git status --short
    git diff --no-ext-diff
    git diff --cached --no-ext-diff
    
  2. Derive the desired commit boundary from the user's request and the diff. Group by logical purpose rather than file count.

  3. 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.
  4. 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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Applies local reliability, viewport, tab-safety, stale-ref, widget, and browser-boundary lessons to every agent-browser automation. Use alongside the upstream agent-browser skill whenever navigating, clicking, filling, testing, extracting, taking screenshots, or debugging any website with agent-browser.

The English summary is being prepared. Showing the original description.

aspiers/ai-config15Updated Oct 9, 2026

Size the agent-browser Chromium window to fill its current screen, leaving a configurable bottom margin for the desktop panel. Use before any agent-browser automation that needs the full screen visible without elements overlapping or scrolling off (e.g. Xero, dense web apps).

The English summary is being prepared. Showing the original description.

aspiers/ai-config15Updated Oct 9, 2026

Create Claude Code slash commands, OpenCode command files, Pi prompt templates, and Codex custom prompts that delegate to the right subagent or skill. Use when creating new commands, porting commands across agent platforms, or refactoring existing commands to follow platform conventions.

The English summary is being prepared. Showing the original description.

aspiers/ai-config15Updated Oct 9, 2026

Adds or changes allowed commands in AI agent permission configs for OpenCode and Claude Code. Use when a command needs adding to an agent's allow list, when permission settings for existing commands need changing, when setting up a new AI tool that requires command permissions, or when the user asks to stop being prompted for a particular command.

The English summary is being prepared. Showing the original description.

aspiers/ai-config15Updated Oct 9, 2026

bc

Free

Creates a Beads issue for a described problem or piece of work without doing the work itself. Use when the user invokes `/bc` or `$bc`, or asks to file, log, or record a bead for something. To also carry out the work, use the `bx` skill instead.

The English summary is being prepared. Showing the original description.

aspiers/ai-config15Updated Oct 9, 2026

bdr

Free

Stores a persistent memory or learning with `bd remember` so it survives across sessions. Use when the user invokes `/bdr` or `$bdr`, or asks to remember, note, or persist an insight in a Beads workspace.

The English summary is being prepared. Showing the original description.

aspiers/ai-config15Updated Oct 9, 2026

See all skills by aspiers

Report a problem with this skill