checkstyle-fixer

Run Checkstyle on the current git diff and generate a timestamped summary report.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/baobaoyeye/skills --skill checkstyle-fixer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: checkstyle-fixer
Source: https://github.com/baobaoyeye/skills/tree/main/checkstyle-fixer
Command: npx skills add https://github.com/baobaoyeye/skills --skill checkstyle-fixer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Checkstyle-Fixer prevents QA regressions by analyzing the current git diff, running Checkstyle on changed files, and generating a timestamped summary report plus a repair plan to guide fixes before commit.

Core Features & Use Cases

  • Diff Analysis: identify changed files (both staged and unstaged).
  • Style Check & Reporting: run the built-in Checkstyle tool and produce timestamped reports.
  • Repair Planning & Auto Repair: generate executable repair steps and apply automatic fixes after developer confirmation.
  • Interactive Verification: allow developers to approve fixes before applying changes.

Quick Start

Trigger a diff check to analyze current changes, run Checkstyle, and generate a timestamped report.

Frequently Asked Questions about checkstyle-fixer

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

FAQPage Schema
How do I run a Checkstyle analysis on my git diff before committing?

To run a Checkstyle analysis on your git diff, trigger a diff check to identify changed files and automatically generate a timestamped summary report plus a prioritized repair plan.

Can Checkstyle automatically fix code quality issues in unstaged changes?

Yes, Checkstyle can automatically fix code quality issues in both staged and unstaged changes by generating executable repair steps and applying fixes after developer confirmation.

Do I need to install Checkstyle separately to generate a code quality repair plan?

No, you do not need to install Checkstyle separately, but the Skill requires an internal setup containing tools/checkstyle-9.3-all.jar and tools/google_checks.xml to generate repair plans.

What is the best way to prevent QA regressions for Java code quality on modified files?

The best way to prevent QA regressions for Java code quality is to analyze the current git diff, run Checkstyle on changed files, and generate a repair plan to guide fixes before commit.

Where does the Checkstyle diff analysis write its timestamped summary reports?

The Checkstyle diff analysis writes its timestamped summary reports and repair plans under the checkstyle_results directory to document identified code quality issues.