gsd-audit-fix

Audit a source, classify findings, and apply verified fixes with atomic commits.

1|Updated Sep 6, 2015
One-click install
npx skills add https://github.com/deerawan/dotfiles --skill gsd-audit-fix-deerawan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-audit-fix
Source: https://github.com/deerawan/dotfiles/tree/main/claude/skills/gsd-audit-fix
Command: npx skills add https://github.com/deerawan/dotfiles --skill gsd-audit-fix-deerawan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns recurring audit findings into verified fixes by automatically determining which issues can be fixed safely versus which require manual review.

Core Features & Use Cases

  • Autonomous audit-to-fix workflow: Runs a targeted audit, classifies findings, and proceeds to fixes for auto-fixable items.
  • Severity- and count-controlled triage: Lets you limit work via severity filtering and a maximum findings cap.
  • Test verification and atomic commits: Ensures changes are validated and recorded cleanly for review or rollback.
  • Use Case: After an “audit-uat” run surfaces configuration or code issues, you can safely apply fixes for the most relevant high/medium problems while isolating manual-only items.

Quick Start

Run the gsd-audit-fix skill with the audit source audit-uat to classify findings and automatically apply fixes with test verification, without committing changes by using the dry-run flag.

Frequently Asked Questions about gsd-audit-fix

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

FAQPage Schema
How do I auto-fix audit findings while keeping test confidence and traceability?

To auto-fix audit findings safely, classify issues into auto-fixable versus manual-only categories, apply fixes, run test verification, and record atomic git commits for clean rollback and traceability.

What is the best way to triage codebase audit issues by severity before applying changes?

Triage codebase audit issues by applying severity filtering and a maximum findings cap to limit work, ensuring you process relevant high or medium problems while isolating manual-only items.

Can I run a classification-only audit on my configuration without committing changes?

Yes, you can run a classification-only audit on configuration files without committing changes by using the optional dry-run flag to evaluate auto-fixable items safely.

How do I ensure automated codebase remediation does not break existing tests?

Ensure automated codebase remediation preserves test confidence by running test verification after applying fixes, which validates changes before they are recorded as atomic git commits.

Does this developer tooling require specific flags to control the audit-to-fix workflow bounds?

Yes, the audit-to-fix workflow requires flags for source specification, severity filtering, and maximum bounds to control the scope of findings processed during codebase remediation.