code_assistant

Writes Groovy and JavaScript scripts for Rierino platform business logic and event processing.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/rierino-open/rierino-claude-plugin --skill code-assistant-rierino-open
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code_assistant
Source: https://github.com/rierino-open/rierino-claude-plugin/tree/main/development/skills/code_assistant
Command: npx skills add https://github.com/rierino-open/rierino-claude-plugin --skill code-assistant-rierino-open

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers on the Rierino low-code platform need to write custom backend scripts and event handlers, but producing null-safe, type-safe Groovy or JavaScript code that matches platform conventions is error-prone without guidance. ## Core Features & Use Cases - Groovy Event Scripting: Generates event-editing scripts using the mandatory ObjectNode payload pattern for processing platform event data. - Defensive Code Generation: Enforces safe-navigation operators, null checks, and explicit type casting in every script. - Convention Alignment: Aligns variable names, field accessors, and entity structures with the platform's CONVENTIONS.MD standards. - Use Case: When you need a Groovy hook that transforms an incoming order payload before it is persisted, the assistant produces a script that safely navigates the event structure and modifies the payload in place. ## Quick Start Ask the assistant to write a Groovy script that processes an event payload and updates a specific field on the entity.

Frequently Asked Questions about code_assistant

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a Groovy script to edit event data in Rierino?▼

Use the mandatory template that accepts a JsonNode event, extracts the payload as an ObjectNode, modifies it, and returns the event. Always apply safe-navigation operators and null checks when accessing fields.

When should I use Groovy versus JavaScript for platform scripts?▼

Use Groovy for backend logic and event processing, and JavaScript for storefront or client-side logic. If the language is ambiguous in a request, the assistant defaults to Groovy for backend tasks.

Can Groovy scripts replace JMESPath for data transformation?▼

Groovy scripts are intended for validation or enrichment logic that exceeds JMESPath capabilities. Simple field mappings and queries should remain in JMESPath; use scripts only for complex conditional or computational logic.

Why does my script fail with null pointer errors on event payloads?▼

Failures occur when fields are accessed without null checks or safe-navigation operators like entity?.field. Always verify the payload node exists before calling getters, and cast values explicitly with methods like .toInteger() before math operations.

What naming conventions must Rierino scripts follow?▼

All variable names, field accessors, and entity structures must align with the platform's CONVENTIONS.MD document. Scripts should reuse provided field names exactly and never invent API methods.