Menu
TRIGGER when user asks to rename the object type or struct used by a SQL CRUD microservice.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
TRIGGER when the user asks to upgrade the project to a newer or the latest version of Microbus, or to update the framework. Each Microbus release ships this one self-contained skill; it applies that release's single-version migration, then chains to the next release's copy of this skill until the target version is reached.
TRIGGER when user asks to create, scaffold, or initialize a new microservice.
How to choose the hostname of a new Microbus microservice. Referenced by the add-microservice and add-sql-microservice scaffolding skills (and, through their delegation to add-microservice, by add-python-microservice and import-openapi-microservice). Consult it whenever a microservice's hostname is being chosen.
Performs an architectural review of a microservice-based system built on the Microbus framework. Covers only cross-cutting, cross-microservice concerns - service boundaries, the dependency graph, coupling, cross-service consistency, data ownership, workflow composition, edge security, and system operations. Anything judgeable inside a single microservice directory belongs to the review-microservice skill and is out of scope here. Produces a structured report with findings and recommendations.
Reviews the microservices touched by a set of changes - by default the whole current feature branch versus its merge-base with main, plus any uncommitted work. Runs the review-microservice skill on each changed microservice and the review-architecture skill scoped to those microservices and their graph neighbors, then consolidates one report. Use before merging a branch or before committing working-tree changes.
Performs a thorough review of a single Microbus microservice. Checks for completeness, framework compliance, code quality, security, test coverage, documentation, API design, and data access performance. Produces a structured report with findings and recommendations.
| name | rename-sql-object |
| description | TRIGGER when user asks to rename the object type or struct used by a SQL CRUD microservice. |
CRITICAL: Read and analyze this microservice before starting. Do NOT explore or analyze other microservices unless explicitly instructed to do so. The instructions in this skill are self-contained to this microservice.
IMPORTANT: MyNoun, MyNounKey, mynoun, and mynounapi are placeholders for the actual object, its key, directory, and API package of the microservice.
Copy this checklist and track your progress:
Renaming the object:
- [ ] Step 1: Read Local CLAUDE.md File
- [ ] Step 2: Update Type Definitions
- [ ] Step 3: Update References
- [ ] Step 4: Alias the Old Type Definitions
- [ ] Step 5: Housekeeping
CLAUDE.md FileRead the local CLAUDE.md file in the microservice's directory. It contains microservice-specific instructions that should take precedence over global instructions.
Find the struct definition of MyNounKey in mynounapi/objectkey.go and rename it to the new name MyNewNounKey.
Find the struct definition of MyNoun in mynounapi/object.go and rename it to the new name MyNewNoun.
Update only the hand-written files; the generated files (mynounapi/client.go, intermediate.go, mock.go, mock_test.go, manifest.yaml) are regenerated from definition.go in Step 5.
Search the hand-written files in mynounapi/ (definition.go and the sibling type files) for references to MyNounKey and MyNoun, and update to MyNewNounKey and MyNewNoun. In definition.go this covers the In/Out struct fields that carry the object/key types (e.g. Obj *MyNoun, ObjKey MyNounKey).
Search the microservice's other hand-written files (service.go, service_test.go) for mynounapi.MyNounKey and mynounapi.MyNoun, and update them.
Search other microservices that consume this type for mynounapi.MyNounKey and mynounapi.MyNoun and update their hand-written definition.go/service.go; their generated files are regenerated by their own housekeeping. The aliases added in Step 4 keep everything compiling in the meantime.
This step intentionally reintroduces the old type names as deprecated aliases for backwards compatibility.
Add a type alias of the old object key to the new object key in mynounapi/objectkey.go
// MyNounKey is an alias to MyNewNounKey.
//
// Deprecated: Use [MyNewNounKey]
type MyNounKey = MyNewNounKey
Add a type alias of the old object to the new object in mynounapi/object.go
// MyNoun is an alias to MyNewNoun.
//
// Deprecated: Use [MyNewNoun]
type MyNoun = MyNewNoun
Follow the housekeeping skill. The renamed object type is referenced by definition.go, so the boilerplate regeneration (genservice) re-emits client.go/intermediate.go/mock.go/mock_test.go/manifest.yaml with the new name.