smithery.ai

ezorm-gen-yaml-mysql

Generate Go code from ezorm YAML (mysql/mysqlr). Prefer mysqlr unless the user explicitly asks for mysql. Provide the exact ezorm CLI command(s).

First seen Apr 11, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,341 B
  • docs SUMMARY.md 173 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Ezorm Gen Yaml (MySQL/MySQLr)

Scope

Generate Go code from ezorm YAML schema files for mysql/mysqlr using the ezorm CLI. Prefer mysqlr unless the user explicitly requests mysql. Read these files when command details or examples are needed:

  • Makefile (target: gene2e)
  • e2e/mysql/
  • e2e/mysqlr/

If the local references/ or assets/ directories are missing, run: scripts/init.sh (or scripts/init.sh --force to refresh). Validate with scripts/validate.sh. If bin/ezorm is missing, run scripts/ensure-ezorm.sh first.

Workflow

  1. Confirm input YAML path(s) and output directory.
  2. Choose goPackage and namespace (required for ezorm gen).
  3. Use the mysql/mysqlr command pattern:

- mysql: bin/ezorm gen -i <yaml-or-dir> -o <out-dir> --goPackage <pkg> --namespace <ns> - mysqlr: bin/ezorm gen -i <yaml-or-dir> -o <out-dir> --goPackage <pkg> --namespace <ns>

  1. Output only the command(s) needed. Do not generate Go code in the response.

Output Rules

  • Emit shell command(s) only.
  • Do not invent paths; use the user-provided locations.
  • Prefer a single command per directory when input is a folder.