skill-improve

Automate testing and fixing by running an improvement loop that executes static checks, applies targeted fixes to failing sections, and reruns tests to decide whether to keep or rollback changes.

The iterative improvement process handles static checks by evaluating static scores across multiple cycles, identifying failures and warnings, and proposing targeted edits without rewriting passing parts.

Yes, you can rollback changes if a fix lowers the quality-assurance score. The re-test and decision mechanism reruns static tests after applying fixes and automatically rolls back changes that do not improve the score.

The best way to ensure frontmatter integrity is to use an automated improvement loop that validates frontmatter structure during targeted edits, ensuring repeatable re-evaluation using the Skill Testing Framework.

No external dependencies are needed to run the retesting workflow. The improvement cycle operates independently to execute static checks, apply fixes, and re-evaluate results without requiring additional tool installations.

The automated fix process avoids rewriting passing sections to preserve working logic and prevent regressions. It proposes changes strictly to failing sections identified during the static check evaluation phase.