Git commit commands: A focused Git commit workflow with staging, reviewing changes, writing commits, amending the latest local commit and inspecting results. This guide explains what each command does, its syntax, practical examples, useful options, and common mistakes. Commands are shown for typical installations; flags can vary across operating-system and tool versions.
Before you start
Open a terminal appropriate for the operating system shown in the examples. Check that the required tool is installed and that you are running it with the permissions needed for your task. Replace sample names, paths, hostnames and IDs with values from your own environment.
Syntax at a glance
Square brackets usually indicate optional arguments, while uppercase words such as FILE, HOST and PACKAGE are placeholders that you replace. Keep quotes around paths or text that contains spaces. Commands should be tested on a safe sample before being used in production.
Quick command reference
| Command | What it does | Example | Useful options |
|---|---|---|---|
git add | Stage selected edits | git add src/ | -p stages interactive hunks; -A stages all changes |
git diff --staged | Inspect changes prepared for a commit | git diff --staged --stat | --stat summarizes file changes |
git commit | Create a commit from staged files | git commit -m "Add command reference page" | --signoff adds a sign-off line; --amend rewrites the previous commit |
git commit --amend | Edit the latest commit | git commit --amend -m "Clarify installation instructions" | --no-edit reuses the existing message |
git show | Inspect a commit and its patch | git show --stat HEAD | --name-only lists changed paths; --format controls metadata |
Command syntax and examples explained
1. git add
Purpose: Stage selected edits.
Syntax
git add PATHExample
git add src/Options and notes: -p stages interactive hunks; -A stages all changes.
Review the staged diff before committing.
2. git diff --staged
Purpose: Inspect changes prepared for a commit.
Syntax
git diff --stagedExample
git diff --staged --statOptions and notes: --stat summarizes file changes.
This helps catch secrets or accidental unrelated edits before commit.
3. git commit
Purpose: Create a commit from staged files.
Syntax
git commit -m MESSAGEExample
git commit -m "Add command reference page"Options and notes: --signoff adds a sign-off line; --amend rewrites the previous commit.
Write a message that explains the intent of the change.
4. git commit --amend
Purpose: Edit the latest commit.
Syntax
git commit --amendExample
git commit --amend -m "Clarify installation instructions"Options and notes: --no-edit reuses the existing message.
Amending changes commit identity/hash; avoid rewriting a commit already shared unless agreed.
5. git show
Purpose: Inspect a commit and its patch.
Syntax
git show COMMITExample
git show --stat HEADOptions and notes: --name-only lists changed paths; --format controls metadata.
Use this to verify what a commit actually contains.
Common mistakes and troubleshooting
- Command not found: confirm the tool is installed and available on your PATH; open a new terminal after changing PATH.
- Permission denied: verify the current account, file permissions and target path. Use administrator/root privileges only when genuinely required.
- Unexpected output: check the command version, quoting, current directory and exact arguments. Consult the local help or manual for options supported by your build.
- Destructive operations: preview the target and keep a backup before deleting data, rewriting history, flashing a partition or changing system configuration.
Safety tips
Review every command before running it, especially commands that delete files, change permissions, flash firmware, alter a database or expose a network service. For network scanning and remote administration, work only on devices and systems you own or are authorized to test. Keep credentials, private keys, access tokens and log files private.
Frequently asked questions
Do these commands work on every system?
Not always. Some commands are specific to Windows, Linux, Android, a particular package manager or an installed tool version. Use the syntax shown for your platform and check local help when a flag is unavailable.
Can I copy and run every example exactly?
Use the examples as templates. Replace placeholders such as filenames, package IDs, hostnames and paths with your own values, and verify the effect before executing a command that changes data or system state.
Conclusion
Use this reference as a starting point, then confirm flags in the tool’s official help or manual for your installed version. A clear understanding of syntax, options and side effects makes command-line work more reliable.