gsd-audit-fix

Automates remediation of audit findings by classifying and applying verified fixes with atomic commits.

4|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/lgwanai/openforce --skill gsd-audit-fix-lgwanai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-audit-fix
Source: https://github.com/lgwanai/openforce/tree/main/skills/gsd-audit-fix
Command: npx skills add https://github.com/lgwanai/openforce --skill gsd-audit-fix-lgwanai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fixing codebase audit findings is slow and error-prone when the work requires triaging, editing multiple files, validating behavior, and producing reviewable commits.

Core Features & Use Cases

  • Issue classification: Separates findings into auto-fixable vs manual-only categories so you know what can be safely handled end-to-end.
  • Autonomous remediation: Applies fixes for auto-fixable issues, then verifies changes using tests before finalizing.
  • Atomic commit output: Produces commits that keep changes reviewable and traceable back to specific findings.
  • Use Case: When you run a security or quality audit on an existing repository, this skill turns eligible findings into validated fixes while leaving the rest clearly marked for human follow-up.

Quick Start

Run the audit-and-fix pipeline with high-priority coverage by executing the command: openforce gsd-audit-fix --source audit-uat --severity high --max 5

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 fixing code audit findings for security and quality issues?

You can automate fixing code audit findings by classifying issues into auto-fixable versus manual-only categories, applying deterministic fixes, verifying changes with tests, and generating atomic commits for reviewable remediation.

Can I dry run an audit remediation to preview auto-fixable issues before applying changes?

Yes, you can run a dry-run mode to preview auto-fixable issues. This mode outputs a classification table only, allowing you to triage security and quality findings without modifying repository code or committing changes.

What is the best way to ensure automated security remediation does not break existing code?

The best way to ensure safe security remediation is using test verification alongside atomic commits. Applying deterministic fixes and validating behavior before finalizing commits keeps code changes reviewable and prevents regression.

Does audit remediation support severity thresholds and finding limits for code quality checks?

Yes, audit remediation supports severity thresholds and finding limits. You can control the pipeline by specifying severity levels like high and setting a maximum finding count to focus on the most critical security and correctness issues.

How are manual-only audit findings handled during automated code quality remediation?

Manual-only audit findings are clearly marked and left for human follow-up. The automated remediation pipeline separates these from auto-fixable issues, ensuring only deterministic, verified fixes are applied to repository code.