菜单
Launch and manually verify ClamAV UI after a change — single-instance/tray behavior, what to click through, and the Windows Defender/EICAR gotcha. Use after building when a change needs to be seen working in the real app.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Version bumps and releases of ClamAV UI — AssemblyInfo.cs, the release.yml workflow, vX.Y.Z branch flow, and the self-update constraints a release must respect. Use when bumping the version, preparing a release, or changing anything about update/release plumbing.
Retake the four README screenshots (dashboard, logs, quarantine, settings) by driving the running ClamAV UI app through UI Automation. Use when asked for new/updated README screenshots or to capture the app's pages.
Add or change user-visible text in ClamAV UI — Lang.cs keys, English+Ukrainian translations, ApplyLanguage re-texting. Use whenever any UI label, button, log line, tray balloon, status message, or dialog string is added or edited.
Add a persisted option to ClamAV UI — a settings.ini key with LoadSettings/SaveSettings wiring, migration for old settings files, and a control on the Settings page (absolute-positioned card layout). Use when adding a toggle, selector, or any state that must survive restarts.
Add or run unit tests for ClamAV UI — the zero-dependency runner in tests/TestFramework.cs, making logic testable via internal static helpers, TempDir usage. Use when writing tests, making code testable, or investigating test failures.
| name | verify |
| description | Launch and manually verify ClamAV UI after a change — single-instance/tray behavior, what to click through, and the Windows Defender/EICAR gotcha. Use after building when a change needs to be seen working in the real app. |
Build first (.\build.ps1), then launch .\ClamAVUI.exe.
Stop-Process -Name ClamAVUI, then launch again.Stop-Process).--tray starts minimized to the tray (this is what autostart uses).clamav/ next to the exe (gitignored,
~220 MB); without it most scan paths are disabled but the UI still runs.settings.ini asks the portable-vs-install question
(per-user install to %LocalAppData%\Programs\ClamAV UI, no UAC). To test
upgrade behavior, keep the existing settings.ini; to test first-run
behavior, move it aside temporarily (it's gitignored). Careful: answering
YES actually installs and relaunches from the per-user folder.ApplyLanguage() must re-text them, and the longer
Ukrainian strings must not clip or overlap.settings.ini next to the exe shows the raw value).Windows Defender intercepts EICAR test files before clamscan can see them — on a machine with Defender active, don't use EICAR to test detection or quarantine flows. Verify scan plumbing with a clean file instead (the log/summary/threat-count paths are the same), or use a Defender exclusion folder you control.