stage

Stages Git files interactively or by direct specification, avoiding bulk adds and validating afterward.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/LarryHsiao/Skadi --skill stage-larryhsiao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stage
Source: https://github.com/LarryHsiao/Skadi/tree/main/skills/stage
Command: npx skills add https://github.com/LarryHsiao/Skadi --skill stage-larryhsiao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stage local files to Git by showing unstaged and untracked files and letting you pick which to stage.

Core Features & Use Cases

  • Show unstaged and untracked files before staging.
  • Let you select specific files to stage, avoiding bulk adds.
  • Supports direct file specification for quick operations in scripts or workflows.

Quick Start

Stage the specified files or interactively select unstaged and untracked files to stage.

Frequently Asked Questions about stage

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

FAQPage Schema
How do I stage specific files in Git instead of adding everything?

To stage specific files, you can interactively select from a displayed list of unstaged and untracked files, or specify filenames directly. This avoids bulk adds by letting you pick exactly what to stage.

Can I see unstaged and untracked files before staging them?

Yes, you can see unstaged and untracked files before staging. The tool shows both categories of files, allowing you to review changes and select exactly which ones to stage.

What is the best way to avoid bulk Git adds in my workflow?

The best way to avoid bulk Git adds is to use selective staging. By showing unstaged and untracked files for interactive selection, you ensure only intended changes are staged and validated.

Does this selective staging method support direct file specification for scripts?

Yes, selective staging supports direct file specification. This allows you to quickly stage targeted files within scripts or automated workflows without interactive prompts.

How does this workflow validate the repository state after staging?

After staging, the workflow validates the repository state to ensure safe operations. This mechanism enforces safe staging by confirming the repository status following your selective file additions.

When should I use selective staging instead of standard Git add?

Use selective staging when you have mixed changes and want to avoid bulk adds. It is ideal when you need to interactively pick or directly specify unstaged and untracked files to stage safely.