Porcelain and Plumbing

What

Git’s command suite is architecturally divided into two categories:

• Porcelain: High-level, developer-friendly commands designed for everyday project management and code versioning.
• Plumbing: Low-level, utility-focused commands that perform raw, direct manipulations on the underlying Git database structure.

How

As a developer, you will spend 99% of your time interacting with porcelain commands:

# Common Porcelain Commands
git status   # Check current state of repository
git add      # Stage changes
git commit   # Save snapshots of staged changes
git log      # View history of commits

Under the hood, Git runs plumbing commands to construct the repository’s database objects:

# Common Plumbing Commands (rarely run manually)
git hash-object   # Compute unique SHA-1 hash for a file and store it
git cat-file      # Inspect content/type of internal Git objects

Why

Git was originally designed as a toolkit of low-level commands (plumbing) to build file management systems, and the user-friendly interface (porcelain) was added on top later. Understanding this division helps you realize that high-level Git commands are just abstractions over a simple, elegant database of files.

Summary

Porcelain commands are the user-facing tools for daily coding, while plumbing commands are the internal engines that drive Git’s file system underneath.