skills.rest
axel-kaliff
axel-kaliffCOMMUNITY
Explore all skills by this author →
GitHub

fix-all

Analyze code, apply fixes, run tests, and prepare verified commits.

Updated Sep 9, 2024
Search Tags:#automation#testing#commit#analysis#pipeline#code-review#regression-safety
One-click install
npx skills add https://github.com/axel-kaliff/dotfiles --skill fix-all-axel-kaliff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix-all
Source: https://github.com/axel-kaliff/dotfiles/tree/main/claude/.claude/skills/fix-all
Command: npx skills add https://github.com/axel-kaliff/dotfiles --skill fix-all-axel-kaliff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the find-fix-verify cycle by analysing code, applying automated fixes, running tests with coverage checks, and offering to commit only when the repository is clean, reducing manual cleanup before PRs or merges.

Core Features & Use Cases

  • Composite Pipeline: Chains analyse → review-fix → test → report and skips unnecessary steps when the analysis is already clean.
  • Regression Safety & Guardrails: Re-runs analysis after fixes, halts on regressions, failing tests, or insufficient diff-coverage, and always requests explicit user confirmation before committing.
  • Use Case: Use after completing a feature or before opening a pull request to automatically fix lint/static issues, validate test suites and coverage, and prepare a verified commit.

Quick Start

Run fix-all on the target file or directory to automatically analyse issues, apply fixes, run tests with coverage checks, and offer to commit if all checks pass.

Frequently Asked Questions about fix-all

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

FAQPage Schema
How do I automate code fixes and run tests before a pull request?▼

To automate pre-PR cleanup, you can run a composite pipeline that analyses code, applies automated fixes, runs tests with coverage checks, and prepares a verified commit if all checks pass.

What is an automated find-fix-verify cycle for code cleanup?▼

An automated find-fix-verify cycle chains code analysis, automated fixes, and test execution together, re-running analysis after fixes to halt on regressions or failing tests before offering to commit.

Can I run automated lint fixes and test coverage checks on a specific directory?▼

Yes, you can apply the pipeline to a specified file or directory scope, changed files, or a Python codebase to automatically fix lint and static issues and validate test coverage.

Does the pipeline abort if tests fail or diff coverage is insufficient after fixes?▼

Yes, the pipeline re-runs analysis after applying fixes and halts on regressions, failing tests, or insufficient diff coverage, always requesting explicit user confirmation before committing.

What's the best way to prepare a verified commit after fixing static analysis issues?▼

The best way is to use an end-to-end pipeline that applies automated fixes, re-runs analysis to check for regressions, validates test suites and coverage, and prepares a commit only when the repository is clean.

Related Skills

Explore More Software Engineering Skills→
WesleySmitsWesleySmits
6

generating-unit-tests

Generates and validates unit tests for changed files across your codebase.

Community
Advanced
bestbest
5

code-reviewer

Enforce a standardized code review checklist across local diffs and pull requests.

Community
Intermediate
aniruddh2003aniruddh2003
1

speckit.checker

Run static analysis tools to detect security vulnerabilities, type errors, and linting issues.

Community
Intermediate
kirich1409kirich1409
23

write-tests

Orchestrate retroactive test generation and verification for uncovered code.

Community
Advanced