git_status

Report staged, unstaged, and untracked files from git status --porcelain.

8|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/OpenAuthority/clawthority --skill git-status-openauthority
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git_status
Source: https://github.com/OpenAuthority/clawthority/tree/main/examples/skills/git_status
Command: npx skills add https://github.com/OpenAuthority/clawthority --skill git-status-openauthority

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Returns a quick, structured snapshot of the current git repository state by reporting staged, unstaged, and untracked files, helping you decide next steps without modifying the working tree.

Core Features & Use Cases

  • Three-file-state reporting: provides lists of files in the staged, unstaged, and untracked categories derived from git status --porcelain.
  • Non-destructive inspection: reads repository state without altering any files or history.
  • Use Case: before committing, pulling, or reviewing changes, quickly assess what has changed and what remains untracked.

Quick Start

Run the git_status tool in your repository to obtain the current working tree status including lists of staged, unstaged, and untracked files.

Frequently Asked Questions about git_status

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

FAQPage Schema
How do I check my git repository status for staged and unstaged files?

The best way to inspect a git repository for untracked files is using git status --porcelain, which outputs a structured summary categorizing files into staged, unstaged, and untracked states. This allows you to quickly assess your working tree before committing.

Can I check git working tree state without modifying files?

Yes, you can check your git working tree state without modifying files by reading the repository status. Commands like git status --porcelain perform non-destructive inspection, providing lists of changed and untracked files while leaving your working tree completely unaltered.

How do I review changes in a git repository before committing?

To review changes in a git repository before committing, run a status check to separate files into staged, unstaged, and untracked categories. This structured reporting helps you quickly assess what has changed and decide what needs to be added or committed next.

Does git status work for AI-assisted development workflows?

Yes, git status works for AI-assisted development workflows by providing a structured summary of the working tree state. It reads repository changes and outputs categorized file lists suitable for AI-assisted decision making before performing VCS operations.

What are the limitations of using git status to assess repository changes?

A limitation of using git status to assess repository changes is that it only reports file states as staged, unstaged, or untracked. It does not show the actual line-by-line content diffs, so you need additional commands to review the specific code modifications before committing.