Debug legacy Guitar Pro files with AI
Trace a GP3, GP4 or GP5 read/write mismatch in scorelib and test whether a selected musical detail survives a round trip.
Debug legacy Guitar Pro files with AI by finding the first point where a musical detail changes. A bend might already be missing when a GP5 file is read, or it might disappear only after the library writes a new copy. The gp-legacy-format skill maps these questions to the corresponding parts of the public Rust project.
Keep the test small. A score with one track and a recognisable effect is often more useful than a complete arrangement. Make the assertion about what the musician expects to see, then check the same value after reading, writing and reopening the file.
What it does
- Locate the reader and writer for a particular legacy version.
- Compare version-specific behaviour for a note or measure.
- Follow a track setting through import and export.
- Turn a missing musical effect into a repeatable test.
- Check older fixtures when changing the handling of a later format.
Install and use
- Provide an authorised scorelib checkout, a suitable Rust toolchain and a permitted sample score. Keep the source file available for comparison.
- Ask, “The bend on the third note vanishes after a GP5 round trip. Show where the parsed and reopened notes first differ.”
- Review the proposed change beside its matching read or write path, then repeat the check on the affected versions.
FAQ
Source
Made by slundi. Original skill: gp-legacy-format, published on Codeberg under the MIT licence.
View on Codeberg