audit-and-fix-uncommitted-changes

Audit and iteratively fix uncommitted working-tree changes until no actionable findings remain.

9|1|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/conn-castle/agent-layer --skill audit-and-fix-uncommitted-changes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit-and-fix-uncommitted-changes
Source: https://github.com/conn-castle/agent-layer/tree/main/internal/templates/skills/audit-and-fix-uncommitted-changes
Command: npx skills add https://github.com/conn-castle/agent-layer --skill audit-and-fix-uncommitted-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit and iteratively fix all uncommitted working-tree changes until a confirming review finds no remaining actionable issues. Use when the agent needs to stabilize in-progress diffs from any author or process, run repeated review/fix cycles, and deliver a round-by-round severity report of what was found and fixed.

Core Features & Use Cases

  • Orchestrates end-to-end audit-and-fix cycles across the full working tree with per-round artifacts
  • Supports iterative review, targeted fixes, and round-by-round confirmation until convergence
  • Provides a master report and strict run-id based artifact management to track progress

Quick Start

Run the audit-and-fix loop on the current repository to start converging uncommitted changes.

Frequently Asked Questions about audit-and-fix-uncommitted-changes

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

FAQPage Schema
How do I audit and fix uncommitted changes in my working tree?▼

To audit and fix uncommitted changes, this Skill orchestrates iterative review and fix cycles across your working tree until a confirming round finds no actionable issues. It produces a master report and a strict run-id for traceability.

What is an iterative audit cycle for uncommitted working tree changes?▼

An iterative audit cycle is a round-by-round process of reviewing uncommitted changes, applying targeted fixes, and confirming convergence. It leverages per-round artifacts and convergence rules to ensure no actionable findings remain.

How do I stabilize in-progress diffs before committing them to a repository?▼

You can stabilize in-progress diffs by running the audit-and-fix loop on your current repository. This process applies iterative review and fix cycles to your uncommitted changes until they converge and produce a stable working tree.

Can I track the progress of fixing uncommitted changes across multiple review rounds?▼

Yes, you can track progress using strict run-id based artifact management and per-round artifacts. The Skill generates a master report that details the severity of findings and fixes discovered during each review round.

Does this audit and fix process work with any code repository that has ongoing work?▼

Yes, this process applies to code repositories with ongoing work. It is designed to stabilize in-progress diffs from any author or process by running repeated review and fix cycles until convergence is achieved.