parse-git-status

Parse git status output into structured JSON with branch and file categories.

243|40|Updated Nov 11, 2025
One-click install
npx skills add https://github.com/maslennikov-ig/claude-code-orchestrator-kit --skill parse-git-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parse-git-status
Source: https://github.com/maslennikov-ig/claude-code-orchestrator-kit/tree/main/.claude/skills/parse-git-status
Command: npx skills add https://github.com/maslennikov-ig/claude-code-orchestrator-kit --skill parse-git-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill parses git status output into a structured object with branch, ahead/behind, and file categories.

Core Features & Use Cases

  • Branch tracking parsing: Detect current and upstream branches.
  • Status categorization: Separate staged, modified, untracked, and renamed files.
  • Pre-flight checks: Validate clean working directory before commits.

Quick Start

Input a porcelain status output and receive a structured status report.

Frequently Asked Questions about parse-git-status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I parse git status output into structured data?

Parse git status output by converting porcelain format into a JSON object with fields for branch, tracking information, ahead/behind counts, and file categories—staged, modified, deleted, renamed, and untracked files—enabling programmatic access to repository state.

How can I validate a clean working directory before committing?

Use git status parsing to perform pre-flight checks that detect uncommitted changes, staged files, and untracked files. A clean status confirms no modified, deleted, or untracked items exist, making it safe to proceed with commits or deployments.

What information does git status parsing extract from branch tracking?

Git status parsing extracts the current branch name, upstream branch, and tracking metrics—ahead and behind counts relative to the remote. This reveals synchronization status and helps identify unpushed or unpulled commits.

Can I categorize changed files by their git status type?

Yes, parsing git status separates files into distinct categories: staged changes ready for commit, modified files with uncommitted changes, deleted files, renamed files, and untracked new files. This structured categorization supports selective commit workflows.

What happens when git status parsing encounters invalid input or non-repository contexts?

The Skill includes error handling for invalid git status output and non-repository contexts, returning appropriate error signals rather than failing silently. This ensures reliable integration into automated workflows and validation pipelines.

Why parse git status instead of reading it as plain text?

Structured parsing converts unformatted text into machine-readable JSON, enabling conditional logic, filtering, and integration with other tools. Automation pipelines, CI/CD systems, and validation checks depend on this structured format for reliable decision-making.