scm-triage

Audit git status to classify changes into signal, noise, ghosts, and mailbox.

Updated Nov 30, 2025
One-click install
npx skills add https://github.com/poisontr33s/chthonic-archive --skill scm-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scm-triage
Source: https://github.com/poisontr33s/chthonic-archive/tree/main/.codex/skills/scm-triage
Command: npx skills add https://github.com/poisontr33s/chthonic-archive --skill scm-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit git status to separate signal, noise, ghosts, and mailbox changes.

Core Features & Use Cases

  • Classify changes into SIGNAL, NOISE, GHOST, and MAILBOX.
  • Generate deterministic triage plans and pre-nuke clarity snapshots for Codex lane recovery.
  • Produce snapshots and guidance before risky edits, reloads, or large commits.

Quick Start

Run the scripts/scm_triage.py script to audit the repository state and generate a triage plan or Codex recovery snapshot.

Frequently Asked Questions about scm-triage

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

FAQPage Schema
How do I audit git status to separate signal from noise before a large commit?

You can audit git status by running the scm_triage.py script to classify repository changes into signal, noise, ghosts, and mailbox categories, producing a deterministic triage plan before risky edits or large commits.

How do I generate a deterministic triage plan and recovery snapshot for git changes?

Generate a triage plan and recovery snapshot by executing the scm_triage.py script with audit modes like --plan or --full, which writes deterministic, path-based outputs under the codex/mailbox directory for Codex lane recovery.

What are ghost changes in git status and how do I isolate them?

Ghost changes are isolated by running a git status audit through the scm_triage.py script, which separates these phantom modifications from actual signal and noise to produce a clean, deterministic triage plan.

Can I use this git triage process before risky edits and repository reloads?

Yes, you can and should use this git triage process before risky edits, reloads, or large commits to produce deterministic triage plans and Codex recovery snapshots that ensure repository state clarity.

What is the best way to snapshot mailbox changes in a git repository?

The best way to snapshot mailbox changes is by running the scm_triage.py script with the --snapshot audit mode, which captures mailbox modifications and writes them as deterministic, path-based outputs under codex/mailbox.

Do I need any dependencies to run git status audits for code cleanup?

No external dependencies are required to run git status audits for code cleanup, as the Skill leverages the shared scripts/scm_triage.py script to execute audit modes and generate triage plans independently.