// Use the Zowe Explorer Development CLI (zedc) ONLY when the user explicitly mentions or requests "zedc". Provides sandboxed testing, environment setup, and package management.
| name | zedc |
| description | Use the Zowe Explorer Development CLI (zedc) ONLY when the user explicitly mentions or requests "zedc". Provides sandboxed testing, environment setup, and package management. |
| metadata | {"version":"1.0"} |
zedc is a lightweight CLI built in Rust that facilitates Zowe Explorer development and testing. It is available in the user's PATH.
IMPORTANT: This skill and the zedc tool should ONLY be used when the user explicitly asks for it (e.g., "use zedc to check coverage" or "run zedc setup"). Do not use it proactively for standard agentic development workflows (continue using standard pnpm commands by default).
zedc test provides powerful sandboxed testing capabilities.
Check Test Coverage: zedc test coverage (or zedc test cov)
--verbose (show verbose output), --filter <package> (filter tests to a specific package).Test Local VSIX in Sandbox: zedc test local <file.vsix> (or zedc test l <file.vsix>)
.vsix files.ZOWE_CLI_HOME set to a sandboxed directory so it doesn't affect the user's global configuration.Test GitHub Artifacts: zedc test gh-repo <refs> (or zedc test ghr <refs>)
zedc setup
node_modules.zedc setup --reference <ref>zedc pm <args...>
zedc commands if the user explicitly mentions zedc in their prompt.zedc manually unless it is missing from the PATH. It is already compiled and available as zedc.Write and maintain Vitest unit tests and WDIO/Cucumber end-to-end tests in the Zowe Explorer monorepo. Use when adding, updating, debugging, or reviewing tests, when working with `*.unit.test.ts` files, `__tests__/__unit__/` or `__tests__/__e2e__/` directories, `.feature` files, step definitions, page objects, mock factories (`mockCreators/`), `MockedProperty`, `jest-mock-vscode`, `vitest.config`, `wdio.conf`, or running `pnpm test` / `pnpm test:e2e` in `packages/zowe-explorer/`, `packages/zowe-explorer-api/`, or `packages/zowe-explorer-ftp-extension/`.
Audit pull requests for breaking changes in the Zowe Explorer monorepo. Examines PR descriptions, review comments, and diffs to identify API and behavioral breaking changes, with special sensitivity to packages/zowe-explorer-api. Reconciles labels with user confirmation. Use when asked to audit breaking changes, check for breaking changes, or review a set of PRs for breaking impact.
Refactor, deduplicate, and improve TypeScript code quality in the Zowe Explorer monorepo. Use when refactoring or checking code quality in packages/zowe-explorer/ and packages/zowe-explorer-api/.
Review code changes for functional correctness and regressions in Zowe Explorer. Focuses on tree view actions, filesystem APIs, and extension initialization. Use when validating a completed feature, bug fix, or refactor before merging or release.
Review pull requests for code quality, security, and Zowe conformance. Use when reviewing PRs, examining code changes, checking branch differences, or when the user asks for a code review.