Library change finder
Point it at a Python project. Get which library changes came after the AI's training and where your code uses them.
Library change finder is a free AI skill for the job "Test and fix code". Give the instructions to an AI assistant that supports the required files and tools, then review its output.
Free · No account · CC BY 4.0 licence · Made by sickn33 · Level: advanced
Made by sickn33. See the original on GitHub; we copied it as it is, with its licence.
What it does
AI models write code from what they learned before a cutoff date. If your project pins newer library versions, the model may use old methods. This finds the gap in your Python project and shows where your code is affected. It reads your lockfile, checks the model's cutoff, and lists which pinned libraries changed their interfaces since then. Then it points to the files in your code that call those changed parts. The scan only reads. If you want, it previews short notes for your AGENTS.md or CLAUDE.md and writes them only after you agree. It needs the small since-cutoff tool, which it asks before downloading.
You give it
- A Python project with pinned dependencies
- The AI model you use
- Permission to run the since-cutoff tool
- A yes or no on writing notes (optional)
You get
- The model's cutoff and affected libraries
- Changed interfaces your code uses
- The files that use them
- A previewed notes block for AGENTS.md or CLAUDE.md
Use it when
- Your AI keeps calling library functions that no longer exist.
- You upgraded packages and want to know what the AI may get wrong.
- You want a standing note in your repo about changed library behaviour.
- You maintain a Python project and use a coding agent daily.
How to use it
- Add it to your AI once: download it and add the folder to Claude, ChatGPT or Codex as a skill.
- Ask for the job in your own words. Your AI opens the skill when it fits.
- It works best when your AI can run code and read your project files.