stage

Stage specific files or code hunks for a Git commit.

399|31|Updated Mar 11, 2026

Search Tags:#git #version control #commit #code management #staging

Ready to run

npx skills add https://github.com/tobihagemann/turbo --skill stage-tobihagemann

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: stage
Source: https://github.com/tobihagemann/turbo/tree/main/skills/stage
Command: npx skills add https://github.com/tobihagemann/turbo --skill stage-tobihagemann

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents accidental staging of unrelated changes by allowing precise selection of files and even specific code hunks for a Git commit.

Core Features & Use Cases

Selective Staging: Add only specific modified, added, or deleted files to the Git staging area.
Hunk Staging: Use git add -p for granular control when a file has mixed relevant and irrelevant changes.
Secret Detection: Warns if files containing secrets are about to be staged.
Use Case: After implementing a feature, you might have also made unrelated documentation edits. This skill helps you stage only the feature files, keeping your commit clean.

Quick Start

Stage the files 'src/main.py' and 'tests/test_utils.py' for the next commit.

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 for a git commit without including unrelated changes?▼

To stage specific files for a git commit, you select only the modified, added, or deleted files relevant to your current task. This prevents accidental staging of unrelated documentation or config edits, keeping your commit history focused and clean.

How does hunk staging work for mixed changes in a single file?▼

Hunk staging uses git add -p to interactively review and stage specific code segments within a single file. This allows you to separate relevant feature updates from unrelated edits, ensuring only the necessary code blocks are staged for commit.

Can I prevent staging sensitive files like .env in git?▼

Yes, this staging process detects and warns you if files containing secrets, such as .env, are about to be staged. This secret detection mechanism prevents accidentally exposing sensitive configuration data in your version control history.

What is the best way to keep my git commit history clean during feature development?▼

The best way to maintain a clean git commit history is through selective staging. By precisely staging only the files or code hunks related to a single feature, you avoid mixing unrelated changes like documentation edits into your feature commits.

Does selective staging require any special git configuration or dependencies?▼

Selective staging requires no special dependencies or components. It relies on standard git version control commands, specifically using built-in features like git add and git add -p to manage exactly which code modifications are prepared for the next commit.