Shared field change checker
Name a changed field or flag. Get the places it is missing or read differently, across database, API and apps.
Shared field change checker 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: expert · Thinking: high
Made by sickn33. See the original on GitHub; we copied it as it is, with its licence.
What it does
A read-only report of every place a changed field, status or flag is missing or read differently, across your database, API, apps and analytics. A field added in one schema is not finished until each path agrees on what it means. First you write down what each state means: missing, null, false or zero, true, and an unknown value from a newer version. These are often treated as the same, and they are not. Then it maps the full chain: storage and migration, models, every endpoint and event, web, Android and iOS handling, analytics, tests, rollout and rollback. The result is a list of gaps with evidence. It reports and does not change code.
You give it
- The field, enum or flag that changed
- The repo or repos involved
- The rollout plan and compatibility needs
You get
- A definition of each state
- A map of everywhere the field flows
- A list of gaps with evidence
- Missing test and rollout checks
Use it when
- You added a feature flag and want to be sure every client handles it.
- A new status value could break older app versions.
- The detail endpoint has the field but the list endpoint does not.
- You are about to release a change that touches database, API and mobile.
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 read your project files.