Are the line numbers consistent during multiple staging operations?

Yes, line numbers refer to the working tree positions, which remain stable until the file is edited, allowing you to run multiple staging commands from one diff output.

Does this skill replace my standard Git installation?

No, it is a specialized utility that works alongside standard Git. You should continue using normal Git for viewing changes and staging entire files or hunks.

How is this different from using git add -p?

While 'git add -p' allows you to stage hunks (groups of lines), the git-lines skill provides even finer control by allowing you to stage individual, specific lines within those hunks.

Can I stage multiple files at once?

Yes, the skill supports staging specific lines across multiple files in a single command using the 'git lines stage' syntax.

What are the requirements to use this skill?

This skill requires the 'git-lines' CLI tool to be installed and available in your system's PATH environment variable.

Line-Level Git Staging

Name: Line-Level Git Staging
Author: Omegaice

byOmegaice

Developer Tools

Stages specific lines from git diffs to create precise, semantic commits when standard hunk-level staging is too coarse.

About

The Line-Level Git Staging skill empowers developers to manage version control with surgical precision by integrating the git-lines utility into Claude Code. While standard Git provides hunk-level staging, this skill allows for the selection of individual additions or deletions by specific line numbers, making it indispensable for splitting complex files into multiple unrelated commits. It is specifically designed for scenarios where developers need to perform partial staging, clean up accidental changes within a larger file, or cherry-pick specific logic without including surrounding modifications, ensuring a cleaner and more readable project history.

Key Features

Stage individual additions and deletions by specific line numbers
Seamless integration with standard Git commit workflows
0 GitHub stars
Identify changes with a dedicated line-numbered diff view
Support for range-based staging and multiple line selections
Stable line referencing based on working tree positions

Use Cases

Staging specific lines for commit while leaving temporary debugging statements in the working directory
Splitting a single file containing multiple unrelated logic changes into distinct semantic commits
Partial staging of bug fixes that were mixed with experimental code during development

About

Key Features

Stage individual additions and deletions by specific line numbers
Seamless integration with standard Git commit workflows
0 GitHub stars
Identify changes with a dedicated line-numbered diff view
Support for range-based staging and multiple line selections
Stable line referencing based on working tree positions

Use Cases

Staging specific lines for commit while leaving temporary debugging statements in the working directory
Splitting a single file containing multiple unrelated logic changes into distinct semantic commits
Partial staging of bug fixes that were mixed with experimental code during development