What happens if a fix is marked as Medium confidence?

Medium confidence fixes are skipped and flagged for manual review to ensure no subjective or risky changes are applied automatically.

How are the fix reports named?

Reports follow a 4-part format including the agent family, a unique UUID chain, and a timestamp, ensuring they are easily traceable back to the original audit.

How does the 'mode' parameter work?

The mode parameter acts as a filter for criticality levels, ranging from 'lax' (critical only) to 'ocd' (all findings), allowing you to control the depth of automated fixes.

Does this skill require internet access to apply fixes?

No, the Fixer workflow intentionally lacks web tools to avoid redundancy, instead relying on the Checker's documented verification for maximum efficiency.

What is the maker-checker-fixer pipeline?

It is a three-stage quality assurance pattern where one agent creates (Maker), another audits (Checker), and a third applies validated improvements (Fixer).

Applying Fixer Workflow

Name: Applying Fixer Workflow
Author: wahidyankf

bywahidyankf

•

Productivity & Workflow

Implements a standardized, high-confidence workflow for fixer agents to apply validated changes from audit reports.

About

The Applying Fixer Workflow skill provides a rigorous framework for fixer agents within a maker-checker-fixer quality pipeline. It automates the discovery of audit reports, enforces a strict validation strategy based on confidence levels (High, Medium, False Positive), and supports variable quality thresholds through mode parameters. By emphasizing re-validation before application and generating detailed progressive reports, it ensures that automated code and documentation fixes are safe, transparent, and auditable without the need for constant manual prompts.

Key Features

Tiered confidence assessment (High, Medium, False Positive) to prevent erroneous fixes
Separation of concerns between verification (Checker) and application (Fixer)
Quality-gate mode handling (Lax, Normal, Strict, OCD) for criticality filtering
4 GitHub stars
Automated audit report discovery with manual override support
Progressive fix report generation for real-time auditability

Use Cases

Standardizing the reporting of automated agent activities in complex enterprise environments.
Automating documentation and code fixes based on validated checker audit reports.
Enforcing high-quality standards in CI/CD pipelines using tiered confidence levels.

About

Key Features

Tiered confidence assessment (High, Medium, False Positive) to prevent erroneous fixes
Separation of concerns between verification (Checker) and application (Fixer)
Quality-gate mode handling (Lax, Normal, Strict, OCD) for criticality filtering
4 GitHub stars
Automated audit report discovery with manual override support
Progressive fix report generation for real-time auditability

Use Cases

Standardizing the reporting of automated agent activities in complex enterprise environments.
Automating documentation and code fixes based on validated checker audit reports.
Enforcing high-quality standards in CI/CD pipelines using tiered confidence levels.