메뉴
Run local EWL Development Utility (DU) operations on EWL systems. Use when asked to run DU operations such as sync or update-data against a particular path or system.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Configure opencode on a new development machine for EWL work by creating the global AGENTS.md and granting access to the EWL source, EWL System Manager source, EWL folder, and EWL client systems directory. Use when setting up opencode on a new machine, or when the user asks to bootstrap, initialize, or configure global opencode for EWL.
Database schema migration using FluentMigrator with the EWL Data Migrator project
Inspect and troubleshoot EWL systems hosted in Azure — locating an installation's App Service, Container App Job, and Log Analytics workspace, and reliably reading Container App (data migrator) console and system logs. Use when checking whether a deploy's data migrator ran, reading container logs for a hosted installation, or investigating an installation's Azure resources. Companion to ewl-azure-pipelines, which covers the build/deploy pipelines that create these resources.
Test changes to EWL agent rules, subagents, skills, OpenCode plugins, and MCP tools by driving OpenCode headlessly, capturing transcripts, and cleaning up afterwards. Load this skill when verifying changes to anything under Library\Files\Agent Rules.md, Library\Files\Agents\, Library\Files\Agent Skills\, Library\Files\OpenCode Plugins\, or Library\Files\OpenCode Tools\.
Azure Pipelines CI/CD for EWL systems including build templates, deploy templates, and pipeline code generation
EWL generated data access layer including table retrievals, modifications, row constants, sequences, and caching
| name | du-troubleshooting |
| description | Run local EWL Development Utility (DU) operations on EWL systems. Use when asked to run DU operations such as sync or update-data against a particular path or system. |
Use the local Development Utility/Development Utility.csproj project in this repository.
Resolve Development Utility/Development Utility.csproj against the session's workspace root to get its absolute path. Set the command tool's working directory to the target installation path, then build the local DU, resolve its output path through MSBuild, and execute the DLL directly:
$duProject = '<resolved absolute DU-project path>'
dotnet build $duProject
if( $LASTEXITCODE -eq 0 ) {
$duDll = dotnet msbuild $duProject -getProperty:TargetPath
if( $LASTEXITCODE -eq 0 ) {
dotnet $duDll <operation> <arguments>
}
}
In this command, $duProject is the absolute project path resolved above, and <operation> <arguments> is the requested DU operation. Keep the command tool's working directory set to the target installation for the entire command because the DU uses its process working directory as the installation path. Resolving TargetPath avoids hard-coding a configuration, target framework, runtime identifier, or output-folder layout.
The DU startup banner's installation path is the local EWL source/configuration location, not the target installation. The target is the process working directory set on the command tool.
If the user names a system instead of providing a path, locate it using repository context and nearby system repositories, then identify its EWL installation directory from its configuration. Ask only if multiple plausible installations remain.
For sync, pass:
sync
update-data requires exactly two operation arguments:
update-data <sourceName|Default> <forceNewPackageDownload:True|False>
Unless the user specifies otherwise, use the default source without forcing a new package download:
update-data Default False
Running this operation replaces target data and can leave running applications with stale cached-table data; restart relevant applications afterward when the DU reports cached tables. If a named source is requested, use its exact configured short name in place of Default. If the DU says that the source does not exist, do not guess another name; inspect the configured sources or ask the user.