Borrowing it
Nothing to install: this file belongs to KhourySpecialProjects/odyssey. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/KhourySpecialProjects/odyssey/production/.claude/skills/schema-change-checklist/SKILL.mdgit clone --depth 1 https://github.com/KhourySpecialProjects/odysseyWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/khouryspecialprojects/odyssey/schema-change-checklist)<a href="https://agentmods.dev/skills/khouryspecialprojects/odyssey/schema-change-checklist"><img src="https://agentmods.dev/badge/skills/khouryspecialprojects/odyssey/schema-change-checklist/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/khouryspecialprojects/odyssey/schema-change-checklist"><img src="https://agentmods.dev/badge/skills/khouryspecialprojects/odyssey/schema-change-checklist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00047 | $0.00761 |
| Opus 5.5 | $0.00019 | $0.00304 |
| Sonnet 5.5 | $0.00009 | $0.00152 |
| Haiku 4.5 | $0.00005 | $0.00076 |
Grade A, and why
schema-change-checklist scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Schema Change Checklist
When a Strapi content type schema changes, the ripple effect touches 6-8 files minimum. Missing any one of them causes silent bugs (stale data, missing fields, type errors).
The Checklist
For every schema field change (add, remove, rename, change type):
1. Schema (source of truth)
-
backend/src/api/{type}/content-types/{type}/schema.json— make the change here first
2. TypeScript Types
-
frontend/types/— update the TypeScript interface for this content type - Check if any other types reference this one (grep for the type name in
frontend/types/)
3. Request Functions
-
frontend/lib/requests/{type}.ts— update populate/filter queries to include new fields or remove old ones - Check populate presets:
enrollment-populates.ts,user-populates.ts— do any presets need the new field?
4. Cache Tags
-
frontend/lib/cache-tags.ts— does a new tag need to be added? Does the invalidation matrix docblock need updating? - If a new mutation is added, add
revalidateTag()calls to the corresponding Server Action
5. Server Actions
-
frontend/lib/actions.ts— if the field is writable, does a Server Action create/update it? - Does the Zod validation schema in
frontend/lib/validations/{type}.tsneed the new field?
6. Components
- Grep for the content type name in
frontend/components/— which components render this data? - Do any components need to display the new field or stop displaying a removed field?
7. Tests
- Update mock data in
frontend/testing/mocks/to include the new field shape - Update any tests that assert on the old field structure
- Write new tests for new behavior
8. Reference Docs
-
docs/agent/backend-architecture.md— update the domain model section if a relation changed
Relation Changes (extra steps)
If you're adding or modifying a relation (manyToMany, manyToOne, oneToMany):
- Check both sides of the relation — Strapi requires
inversedBy/mappedByto match - Update populate queries on BOTH content types
- Check if the inverse side's request functions need updating
- Verify the join table (if applicable) is handled correctly
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- today First seen · 82 lines · 47 tokens per session scan A f49402fa3e57
schema-change-checklist is a skill published in the GitHub repository KhourySpecialProjects/odyssey (7 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 761 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-02.
Other skills, from other repositories
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
convex-explain-app
Explain an existing Convex app — data model + relationships, public vs internal functions, auth/ownership model, components, a request→data flow — read from the schema and function surface. Read-only.
platform-custom-field-generate
Use when users create, generate, or validate Salesforce Custom Field metadata. Trigger on custom fields, field types, Roll-Up Summary, Master-Detail/Lookup relationships, formula fields, picklists, dependent (controlling) picklists, referencing a value set from a field, or scoping picklist values per record type; also…
field-service-sobject-create-configure
Headless 360 REST API deployment step for creating sObject records. Handles describe-based field discovery, required-field derivation, entity-relationship ordering, and composite graph transactions. Use this skill when a designer skill (or a user directly) needs to create sObject records after design confirmation…
durable-objects
Build, debug, or review Cloudflare Durable Objects code for persistent state and coordination.
nornicdb-grpc
Drive NornicDB over gRPC — the Qdrant-compatible surface (Collections, Points, Snapshots) plus the additive NornicSearch service. Use when ingesting via Qdrant SDKs, migrating from Qdrant, or running hybrid text+vector search from a non-Bolt client. Covers connection, RPC catalog, collection→database mapping…