git-triage

Classify untracked and uncommitted files into Track, Ignore, Delete, or Keep Local buckets.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/xinye1/xl-skills --skill git-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-triage
Source: https://github.com/xinye1/xl-skills/tree/main/skills/git-triage
Command: npx skills add https://github.com/xinye1/xl-skills --skill git-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the chaos of a dirty working tree by systematically classifying untracked and uncommitted files, preventing accidental commits of junk, secrets, or build artifacts.

Core Features & Use Cases

  • Intelligent Classification: Categorizes files into Track, Ignore, Delete, or Keep Local buckets based on their origin and purpose.
  • Safety-First Workflow: Prevents bulk actions like git add -A, ensuring every change is reasoned and verified before execution.
  • Use Case: Use this when your repository is cluttered with thousands of untracked files after a build, or when preparing a clean state for a handover or final ship.

Quick Start

Ask the assistant to triage the current git status and help you clean up the untracked files in the repository.

Frequently Asked Questions about git-triage

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

FAQPage Schema
How do I clean up untracked files in a messy git repository?

To clean up untracked files in a git repository, you can triage the working tree to classify files into Track, Ignore, Delete, or Keep Local buckets. This systematic classification prevents accidental commits of junk, build artifacts, or secrets by requiring manual verification before executing destructive operations.

What is the best way to sort a dirty git working tree before a final ship?

Sorting a dirty git working tree requires classifying untracked and uncommitted files by their origin and purpose. This triage process categorizes changes into distinct action buckets, ensuring repository hygiene and preventing bulk actions like git add -A from sweeping in unwanted files before a handover.

How do I prevent accidentally committing secrets and build artifacts in git?

Preventing accidental commits of secrets and build artifacts requires a safety-first workflow that reasons through every file change. By categorizing untracked files into distinct buckets and verifying each classification manually, you ensure only intended files are tracked or ignored via gitignore optimization.

Can I use this git triage process for repositories with thousands of untracked files after a build?

Yes, you can use this git triage process for repositories cluttered with thousands of untracked files after a build. It resolves the chaos by systematically categorizing each file into Track, Ignore, Delete, or Keep Local buckets based on its origin and purpose.

Does cleaning up a dirty git working tree require manual verification of file classifications?

Yes, cleaning up a dirty git working tree requires manual verification of file classifications before performing any destructive operations. This safety-first approach ensures every untracked or uncommitted file is reasoned and verified, preventing accidental data loss or improper gitignore assignments.