agentleFS
ejboyejboy/agent-scripts/skills/coilbase-spring-migration/SKILL.md

coilbase-spring-migration

Skill118 starsChanged 2 days agoMITView on GitHub

Assess and carry out bounded Spring Boot JDBC migrations to CoilBase with Avaje Jex using the published migration guide. Identify JPA, presentation and other unsupported mappings that require explicit application decisions.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before adding custom workarounds or parallel application infrastructure, inspect the target version's documentation and API sources and …

    line 22
  2. Distinctive:

    Use the guide sections on wiring, JDBC, transactions, exceptions, configuration and static resources as needed:

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Spring Boot to CoilBase migration

This experimental skill is maintained in Agent Scripts, outside the CoilBase repositories. Work within the user's migration scope, preserving the existing application as an independent baseline.

Establish the reference and contract

Read the published CoilBase migration guide before proposing API usage. It is the technical authority. A matching local checkout can supply the guide and API sources; record its revision and any differences from the published reference. Check the target dependency versions: the guide uses Preview 4 and discusses Jex 3.6 behavior. Do not silently upgrade the application or invent replacement APIs when versions differ.

Inventory routes, response fields and media types, validation, configuration, SQL, schema initialization, background work and lifecycle. Trace actual transaction entrypoints and callers rather than replacing annotations mechanically. Capture existing behavior checks before editing; distinguish source-derived expectations from executed observations.

Migration does not promise one-to-one Spring Boot compatibility. Preserve essential application correctness, business behavior, data integrity, transaction semantics and required security guarantees. Treat framework conveniences and incidental HTTP behavior as explicit application decisions; allow deliberate, documented simplifications when their tradeoffs meet the user's requirements. Prefer idiomatic CoilBase APIs and application architecture over compatibility workarounds with little practical value. Do not silently change externally required behavior or assume compatibility differences are harmless. Jex is the practical default here; CoilBase is not tied to that HTTP stack.

For each affected feature, record: source location and behavior; carry over, adapt, or explicit design required; guide section supporting the mapping; proposed application change; acceptance check and unresolved questions. Preserve controller, service and repository responsibilities where useful.

Apply documented mappings

Before adding custom workarounds or parallel application infrastructure, inspect the target version's documentation and API sources and prefer existing CoilBase lifecycle hooks, extension points and repository patterns where they meet the migration contract.

Use the guide sections on wiring, JDBC, transactions, exceptions, configuration and static resources as needed:

  • Carry over ordinary models, calculations, validation and SQL where dependencies permit. Adapt constructor wiring, HTTP registration, bindings and row mapping explicitly.
  • Choose the business operation's transaction owner. Fetch external data and validate before a short transaction where the contract permits. Keep participating calls on the same RepositoryContext and thread; separate contexts from the same datasource do not imply shared transactions. Review propagation, isolation, read-only hints and rollback rules individually. Direct batch callers need an explicit boundary if repositories only participate.
  • Preserve locks through the outer commit, timestamps, decimals, constraints and ordering. Verify supported database dialects separately.
  • Map business errors explicitly, including media type. For the guide's Jex 3.6 Problem Details pattern, serialize and write after selecting status and content type; ctx.json() chooses application/json and commits headers. Check malformed requests separately.
  • Preserve deployment environment names, defaults and initialization policy. Define database-backed readiness, background startup, shutdown and failed-start cleanup. Enable static serving only where required and test the packaged assets.

Resolve features beyond the guide's JDBC mappings

Spring Data/JPA, entity management, security, Actuator, scheduling annotations and full Spring property/transaction semantics have no established automatic conversion here. Identify the decisions and required evidence before implementing them. Do not introduce a migration framework or transformation engine, or change CoilBase APIs to fit the migration.

For JPA relationships, explicitly decide loading queries and ordering, generated IDs, ownership, write order, cascade replacements, constraints, query count and caching. Multi-query reads alone do not prove snapshot consistency. For server-rendered applications, inventory rendering, form decoding/binding, field errors, redirects, sessions/CSRF, localization and static assets. Resolve only what the requested slice requires; leave unanswered design questions visible.

The PetClinic migration is supporting evidence for these decisions, not a required architecture or an automatic JPA/Thymeleaf recipe. Consult its relevant implementation and contract when using an example. Label application-local workarounds and accepted differences; do not generalize its renderer, session design or SQL loading strategy into CoilBase requirements.

Verify and report

Use independent disposable data for original and migrated applications. Compare HTTP success and errors (including media types), committed rows and invalid-write rejection. Force failure after an earlier write, verify rollback and subsequent recovery; exercise outer transactions and competing edits where relevant. Check initialization, database readiness, shutdown, packaged restart and persistence. Repeat database-specific checks for every claimed backend.

Report changed files and decisions, commands actually run and outcomes, inherited evidence, unsupported patterns, errors and manual corrections, additional knowledge needed beyond the guide, and remaining acceptance gaps. Distinguish functional equivalence from deliberate differences and untested behavior. A passing JDBC example does not validate JPA relationships or presentation. Stop equivalence claims at the tested scope; publication is a separate decision.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.