auto-fix

What This Skill Does

The auto-fix skill for OpenClaw is a powerful automated developer assistant designed to resolve common codebase friction points without human intervention. By analyzing your project environment, it identifies and applies fixes for Linting violations, TypeScript type errors, syntax irregularities, and failing test cases. It acts as an autonomous layer that handles the "noisy" part of development—fixing missing semicolons, upgrading type annotations, reformatting code to meet project standards, and even updating stale test snapshots. When the skill detects an error, it intelligently decides whether the issue is solvable through standard command-line tools like ESLint, Prettier, or Mypy, or if it requires deeper diagnostic capabilities by delegating to the systematic-debug skill.

Installation

To integrate this skill into your environment, use the OpenClaw command-line interface. Open your terminal and run: clawhub install openclaw/skills/skills/sa9saq/auto-fix Ensure your project repository is initialized with Git, as the skill performs safety checks to verify that changes can be tracked or reverted if necessary.

Use Cases

• Pre-Commit Cleanup: Run before pushing code to ensure your codebase meets all linting and styling requirements automatically.
• CI/CD Recovery: When a build pipeline fails due to trivial syntax errors or formatting issues, auto-fix can quickly rectify the environment.
• Dependency Refactoring: After upgrading versions, use this to address common TS2339 property missing errors or to add necessary optional chaining across large files.
• Test Maintenance: Automatically refresh outdated test snapshots when business logic changes, saving developers from the manual chore of updating test expectation files.

Example Prompts

1. "Check the current linting errors in the src directory and fix everything that can be auto-remediated."
2. "I have some TypeScript type errors regarding null values, can you apply optional chaining where appropriate to fix them?"
3. "The tests in my component directory are failing due to outdated snapshots, please update them so the build passes."

Tips & Limitations

This skill is most effective when your project follows standard configurations (ESLint, Prettier, Pytest). While its success rate for linting is exceptionally high (over 90%), complex logical bugs or architectural type mismatches should not be left solely to this skill. Always ensure you are working within a clean Git state, as the skill performs "in-place" modifications. Avoid using this on experimental code where you lack clear test coverage, as the skill may attempt to make changes based on invalid expectations. If an automatic fix results in a broken build, the skill is designed to halt and suggest a hand-off to the systematic-debug module for a more rigorous investigation.