gsd-audit-fix

Automate an audit-to-fix pipeline that converts software issues into verified code changes.

1|Updated May 24, 2026
One-click install
npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-audit-fix-tinner-deinno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-audit-fix
Source: https://github.com/tinner-deinno/innova-skills-lib/tree/main/core/gsd/gsd-audit-fix
Command: npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-audit-fix-tinner-deinno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces the time and effort needed to find software issues and turn them into reliable fixes by running an end-to-end audit-to-commit workflow.

Core Features & Use Cases

  • Audit and classify findings: Detect issues from a specified audit source and separate auto-fixable problems from manual-only items.
  • Autonomous repair with verification: Apply fixes and run tests to confirm behavior, aiming for trustworthy outcomes.
  • Atomic commit workflow: Produce changes in controlled, commit-ready units after verification.

Quick Start

Run gsd-audit-fix to process findings from audit-uat, fix up to 5 medium+ items, verify with tests, and prepare atomic commits.

Frequently Asked Questions about gsd-audit-fix

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

FAQPage Schema
How do I automate code audit fixes and commit them atomically?

To automate code audit fixes, run an end-to-end workflow that classifies findings into auto-fixable versus manual-only items, applies fixes, verifies with tests, and generates atomic commits for controlled, commit-ready units.

What is the best way to classify audit findings by severity before applying fixes?

Classifying audit findings by severity involves filtering detected issues using a severity flag, allowing the pipeline to separate auto-fixable problems from manual-only work and limit the maximum findings processed per run.

Can I run a dry-run to preview automated code fixes before committing?

Yes, you can run a dry-run to preview automated code fixes before committing. The pipeline supports a dry-run flag to evaluate classified findings and proposed fixes without generating final atomic commits.

How do test verification and atomic commits work in an automated fixing workflow?

Test verification and atomic commits work sequentially in an automated fixing workflow by applying fixes to classified findings, running tests to confirm behavior, and packaging verified changes into controlled, commit-ready units.

Does the automated fixing pipeline work with a specific audit source for repository maintenance?

Yes, the automated fixing pipeline works with a specified audit source for repository maintenance by processing findings from designated sources using the source flag to target specific audit outputs.

What are the limitations when processing a maximum number of audit findings?

When processing a maximum number of audit findings, the pipeline limits the count of items addressed per run using a maximum findings flag, restricting the scope of auto-fixable changes and atomic commits generated.