shesha-utils

Use this skill to add essential code quality analyzers to .NET projects, including AsyncFixer, IDisposableAnalyzers, and Microsoft.VisualStudio.Threading.Analyzers with best-practice configurations.

Analyzes a Shesha form configuration JSON and removes dead/obsolete component properties, strips console.log calls from JS code strings, validates property value types, validates the shape of dropdown values items, detects scripts referencing component labels instead of propertyNames, runs layout validations (container dimension overflow, labelCol+wrapperCol span checks, device-specific style path conflicts), validates JavaScript syntax of embedded code strings, auto-fixes API calls missing try-catch by wrapping the function body in try/catch, and auto-fixes API calls in async-context properties that are missing async/await by adding the async keyword and awaiting calls. Falls back to manual review when function structure is ambiguous. Also detects API calls using .then() chaining and flags them for conversion to async/await + try-catch. Use when a form has been migrated, components have been refactored, or you want to clean up stale properties and debug statements.

Creates and scaffolds integration test projects for Shesha framework .NET applications. Sets up xUnit test infrastructure with NHibernate, database fixtures, test modules, and base classes. Detects whether Shesha.Testing NuGet package is available and adapts accordingly — using the package when present, or scaffolding local infrastructure when not. Use when the user asks to create, add, scaffold, implement, or set up integration tests, test projects, or test infrastructure for a Shesha project.

Creates or updates DevExpress reports in a Shesha application from natural-language requirements — instead of hand-configuring them in the front-end report designer. Generates the DevExpress XtraReport definition XML (SQL data source + bands/tables/charts), the report parameters, and a Shesha filter form, then deploys them live to a target site via its API; re-running against an existing report id updates it in place (never deletes/recreates). Calls the generate-sql-query skill for the report SQL and builds the filter form itself. Use when the user asks to "create a report", "update a report", "auto-generate a report", "build a DevExpress report", "add a chart/filter to a report", "change an existing report", "add a report", "scaffold a reporting report", or configure a report without using the designer UI, for the pd-devexpressreporting / DevExpressReporting module.

Documents Shesha .shaconfig configuration packages by extracting their contents and generating a CSV inventory report. Use when asked to document, inventory, audit, list, or report on .shaconfig files, Shesha configuration packages, or Shesha configuration items (forms, permission definitions, reference lists, etc.).

Generates a safe, read-only Microsoft SQL Server (T-SQL) query from a natural-language request against a Shesha database, using the Shesha entity metadata to find relevant tables, build schema context, and validate the result. Ports the Shesha Automate Engine's SQL generator (prompts + validation rules) so it runs directly in Claude Code without the MCP server. Use when asked to "generate a SQL query", "write SQL from natural language", "query the Shesha database", "generate a view or stored procedure", or similar. Produces only SELECT/INSERT/UPDATE — blocks DELETE/DROP/TRUNCATE/ALTER/CREATE/RENAME.

Uses Playwright to set permissions on unsecured Shesha API endpoints via the permissioned-objects admin UI. Restricts write operations to app:Configurator. Use when the user wants to harden, secure, or lock down API endpoints, fix permissioned-objects, restrict access to admin-only services, or add authorization to unprotected app services in a Shesha application.

Links a Shesha backend module as a local project reference for debugging, or unlinks it back to NuGet. Reads Directory.Build.props to detect available modules, creates or updates a Debug solution file, toggles UseLocal* flags, and wraps PackageReference entries in MSBuild Choose/When/Otherwise conditional blocks. Use when asked to "link module for debug", "debug shesha locally", "add project reference for debugging", "switch to local project reference", or "unlink module".

Runs integration tests against a dedicated test database. Handles database provisioning, fast resets, config updates, and test execution. Use when the user wants to run integration tests, test against a real database, or mentions "run integration tests", "run tests", "integration test", or "test database".

Installs the Claude Logger configuration into Claude Code settings.json files — the CLAUDE_LOGGER_API_URL env var, the shesha-utils plugin, and the boxfusion-plugins marketplace. The UserPromptSubmit/PreToolUse/PostToolUse/SessionStart/Stop ingest hooks ship with the plugin (hooks/hooks.json) and reference the bundled cc_logger.py via ${CLAUDE_PLUGIN_ROOT} — no machine-specific absolute path. Each hook runs cc_logger.py, which enriches the event (turn cost, transcript details on Stop) and forwards it directly to the ingest backend — no local server required. Applies the configuration to both the global user settings and the current project settings as an additive merge — creating files where missing, updating these specific values in place where they already exist, and never removing or overwriting unrelated keys. Use when the user asks to set up, install, configure, add, enable, or update the Claude logger, logger hooks, telemetry hooks, or the ingest hooks for Claude Code.

Scans a target project repository for its Shesha modules, looks up each module's full published version and dependency history on the private Boxfusion Azure Artifacts NuGet/npm feed (or the public nuget.org/npmjs.org registries, plus a specific git ref for source extraction, when the repo is specifically shesha-io/shesha-framework), extracts its domain entities/APIs/settings/enums from its own C# source, has a real "what does this module do and what's it for" description authored per module by reading the actual code (falling back to a mechanical name listing only if skipped), and upserts everything into the Shesha.ModuleRegistry backend via the ModuleInfoSearch API (Pinecone-indexed on insert/update). Use when asked to register, sync, publish, or import a project's modules into the module registry.

Set up a Shesha-based project development environment aligned to Boxfusion development standards and best practices. Run this when a new Shesha project has just been created to verify and configure the dev environment.

Creates new Shesha-specific skills by analyzing existing Shesha application code, documentation, and descriptions. Produces properly structured SKILL.md files with supporting reference files following best practices. Use when the user wants to create a new skill for Shesha code generation, workflow patterns, or any Shesha-specific domain by referencing existing implementations.

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

Upgrades a Shesha project to a target Shesha version, resolving the matching version of every other Shesha and Boxfusion module from the private Azure Artifacts feed, updating the backend Directory.Build.props and all frontend @shesha-io/* packages, then restoring, building and installing to verify. Use when the user wants to upgrade, update, bump or migrate Shesha, BoxStack or Shesha module versions, or asks which module versions are compatible with a given Shesha version.