git-porcelain-parsing

To parse git status porcelain output reliably, you extract status tokens and file paths while handling edge cases like leading spaces, dots, and renamed paths. This Skill processes the raw format into a consistent, machine-parseable structure.

Parsing git porcelain output fails with non-ASCII names because git defaults to quoting unicode paths. This Skill prevents the issue by applying per-command core.quotepath=false to preserve Cyrillic and other unicode characters.

The correct way to parse renamed files in git status porcelain is to detect the 'R' status token and split the path string to separate old and new file names. This Skill handles the extraction of renamed paths automatically.

Yes, you can use git porcelain parsing for pre-commit hooks and CI workflows. This Skill provides precise change data for staged, unstaged, and untracked files, making it suitable for repository auditing and automation tasks.

Yes, git porcelain parsing handles Windows path normalization by converting backslashes to forward slashes. This ensures the extracted file paths remain consistent and compatible across different operating systems.

Common pitfalls when parsing git status --porcelain output in Python include using incorrect string slicing like line[2:] instead of line[3:], which breaks on paths with leading spaces. This Skill documents these issues and provides reliable extraction logic.