Code Assist Skills (enactor-code-assist)

These skills come from the enactor-code-assist child plugin: semantic codebase search plus generation of entities, actions, processes, and tests, powered by the MCP index servers. You don't install it directly - Claude installs it on demand the first time you ask for Enactor code work.

The remote index needs a sign-in

Codebase search runs against Enactor's hosted index server, a shared, internet-reachable service. The first time Claude Code connects, it opens a browser and asks you to log in with the Enactor account your Enactor contact provides. You stay signed in across sessions, so you should rarely be prompted again. See Verify MCP connections in the Setup Guide for the full flow.

The golden rule

When in doubt, use /assist. Describe what you want in plain English and it figures out what you need, then runs the right skill(s) for you.

Build & search skills

Skill	Use it when...
/assist	Your main entry point. Any Enactor implementation task. It figures out what you need and runs the right skill(s). (When in doubt, use this one.)
/create-action	You need a business-logic action (validation, lookup, process step) that plugs into the Enactor process framework. Generates the IUIAction Java class + Process XML registration.
/create-process	You're building a UI workflow, sign-on flows, popups, prompts, or any POS terminal process. Generates the Process Definition XML.
/create-entity-full	You're creating a brand-new entity from scratch. Generates all files: 6 Java classes + 4 XML configs + registration.
/create-entity	You only need the core entity pair: the Interface (I{Entity}.java) and Implementation ({Entity}.java).
/create-entity-key	You're adding key classes (I{Entity}Key.java + {Entity}Key.java) to an existing entity.
/create-entity-server	You're adding database persistence (the Server Interface + DBServer) to an existing entity.
/create-entity-test	You want test coverage for an existing entity (Entity Tests + DBServer Tests).
/validate-entity	You finished creating/editing an entity and want to check all files exist and are consistent.
/test-process	You want unit tests for an existing process. Parses the XML, builds test paths, runs them via Maven until passing.
/create-service-invocation	You need to call/invoke an Enactor service from your code.
/search-codebase	Finding existing code/patterns/utilities before writing anything new. (Also runs automatically inside /assist.)

Setup & config skills

Skill	Use it when...
/init-workspace	First-time plugin setup. Creates/updates CLAUDE.md, bootstraps .mcp.json, checks dependencies, reports environment status. Run on fresh installs or upgrades.
/set-path	Auto-detection picked the wrong codebase folder, or you need to point Claude at a different workspace location.
/set-mcp-server	Search is hitting the wrong branch index (e.g. you're on 2.7 but searching trunk), the index server moved, or you want to "switch index / set MCP url".
/get-session-report	You want session metrics: tokens used, tool-call mix, lines of code produced, commit status, duration, broken down by file type.
/apply-pattern	You want to copy/reuse an existing Enactor pattern from the indexed codebase. Searches the shared index, finds the local file, applies it, builds, and writes a change report. (General-purpose: feature work, bug fix, or refactor.)

Example prompts

You don't need special syntax. Just describe the task. These are real examples:

"How are serial numbers captured and validated in the Enactor codebase?"

"I want to validate the start date in the captured card details. Can we find the related action or validation logic for this in my codebase?"

"I need to add a new column to the ItemInventoryLevel table. The column name should be serialNumber. What files do I need to modify in the codebase to support this change?"

tip

• Building something? Just describe it in plain English and /assist routes it automatically.
• Searching or exploring? Describe what you're looking for and /search-codebase handles it.

Try it yourself

A 5-minute exercise to get comfortable:

1. Search first. In Claude Code, ask: "How is a customer discount applied at the POS? Show me the relevant actions and processes." Watch /search-codebase find the relevant code via the remote index.

2. Generate something small. Run /create-action and describe a simple validation action, e.g.: "An action that validates a captured loyalty card number is 16 digits." Review the generated IUIAction class and Process XML registration.

3. Check your session. Run /get-session-report and look at the tokens used, tool calls, and lines of code produced.

Troubleshooting: search returns results from the wrong branch

Your workspace and the index you're searching are on different branch versions, so the results don't line up with your code. Run /set-mcp-server and switch to the index that matches your workspace branch. See the Setup Guide for how to check the connection, and ask your Enactor contact if you're unsure which endpoint matches your branch.