How do I install the Add Winforms Dialog skill?

Run npx skillmds@latest add gitextensions/add-winforms-dialog in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Add Winforms Dialog safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Add Winforms Dialog?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Add Winforms Dialog free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Add Winforms Dialog?

gitextensions (@gitextensions) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Add Winforms Dialog by gitextensions

Name: Add Winforms Dialog
Author: gitextensions

Add Winforms Dialog

**EXECUTION (runbook) SKILL** — Add a new WinForms dialog/control to Git Extensions following the project's base classes and naming conventions. USE FOR: creating a new Form or UserControl, wiring it to git via UICommands. DO NOT USE FOR: editing existing dialogs' logic only, or non-UI code. Triggers: "add a new dialog", "create a form", "new WinForms control", "new settings page".

File contents

Add a WinForms Dialog (runbook)

Create a new dialog that matches the codebase's conventions. Follow in order.

Steps

Pick the base class (see ui-composition):
- Repo-aware dialog → derive from GitModuleForm (gives UICommands / Module).
- Standard dialog chrome → derive from / use GitExtensionsDialog.
- A panel/control → derive from GitModuleControl.
- NEVER derive directly from raw Form.
Place the files under src/app/GitUI/CommandsDialogs/ (or a suitable subfolder): Form<Name>.cs, Form<Name>.Designer.cs, Form<Name>.resx.
Name controls per ui_design_guidelines.md: btn, lbl, txt, cbx, chk, rb, gbx, tlpnl, flpnl, lnk, …
Talk to git only through UICommands / Module; build commands with Commands.* (structured IGitCommand preferred). NEVER new a GitModule or spawn git directly.
Localize: make every user-facing string a TranslationString, then run the add-translation-strings runbook (update-loc.cmd).
Hotkeys (if any): register via HotkeySettingsManager, not hardcoded key handling (see hotkey-system).
Refresh: after a state-changing action, call UICommands.RepoChangedNotifier.Notify().

Verify

dotnet build /v:q succeeds; control names follow the prefixes.
English.xlf updated (localization gate).
UI touched only on the UI thread (threading-model).

STOP conditions

Deriving from raw Form, hardcoded Colors (use AppColor), or raw git command strings → fix before proceeding.
Add a unit test if the dialog builds git arguments via Commands.*.

---name: add-winforms-dialogdescription: **EXECUTION (runbook) SKILL** — Add a new WinForms dialog/control to Git Extensions following the project's base classes and naming conventions. USE FOR: creating a new Form or UserControl, wiring it to git via UICommands. DO NOT USE FOR: editing existing dialogs' logic only, or non-UI code. Triggers: "add a new dialog", "create a form", "new WinForms control", "new settings page".---# Add a WinForms Dialog (runbook)Create a new dialog that matches the codebase's conventions. Follow in order.## Steps1. **Pick the base class** (see [ui-composition](../../copilot-docs/L1-conceptual/ui-composition.md)): - Repo-aware dialog → derive from `GitModuleForm` (gives `UICommands` / `Module`). - Standard dialog chrome → derive from / use `GitExtensionsDialog`. - A panel/control → derive from `GitModuleControl`. - **NEVER** derive directly from raw `Form`.2. **Place the files** under `src/app/GitUI/CommandsDialogs/` (or a suitable subfolder): `Form<Name>.cs`, `Form<Name>.Designer.cs`, `Form<Name>.resx`.3. **Name controls** per [ui_design_guidelines.md](../../ui_design_guidelines.md): `btn`, `lbl`, `txt`, `cbx`, `chk`, `rb`, `gbx`, `tlpnl`, `flpnl`, `lnk`, …4. **Talk to git** only through `UICommands` / `Module`; build commands with `Commands.*` (structured `IGitCommand` preferred). **NEVER** `new` a `GitModule` or spawn `git` directly.5. **Localize:** make every user-facing string a `TranslationString`, then run the [add-translation-strings](../add-translation-strings/SKILL.md) runbook (`update-loc.cmd`).6. **Hotkeys (if any):** register via `HotkeySettingsManager`, not hardcoded key handling (see [hotkey-system](../../copilot-docs/L2-core-platform/hotkey-system.md)).7. **Refresh:** after a state-changing action, call `UICommands.RepoChangedNotifier.Notify()`.## Verify- `dotnet build /v:q` succeeds; control names follow the prefixes.- `English.xlf` updated (localization gate).- UI touched only on the UI thread ([threading-model](../../copilot-docs/L1-conceptual/threading-model.md)).## STOP conditions- Deriving from raw `Form`, hardcoded `Color`s (use `AppColor`), or raw git command strings → fix before proceeding.- Add a unit test if the dialog builds git arguments via `Commands.*`.

Frequently asked questions