Translation Source Sync
Devolutions/UniGetUI
Synchronizes the UniGetUI English language file with source-code usage, identifies missing translation keys, removes unused entries, reports localization drift, and can reorder locale files to match…
Phase E of a WinForms-to-Avalonia migration: verify behavioral parity against Phase A contracts, record intentional differences, validate supported environments and packaging, and make…
GPL-3.0Auto-check passed
Install Wfa Parity Verify
$ npx skills add tautcony/ChapterTool --skill wfa-parity-verify -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tautcony/ChapterTool wfa-parity-verify --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/tautcony/ChapterTool.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/wfa-parity-verify .claude/skills/wfa-parity-verify && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "wfa-parity-verify" agent skill from https://github.com/tautcony/ChapterTool/tree/master/.codex/skills/wfa-parity-verify into .claude/skills/wfa-parity-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wfa-parity-verify", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/tautcony/ChapterTool/tree/master/.codex/skills/wfa-parity-verifyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add tautcony/ChapterTool --skill wfa-parity-verify -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tautcony/ChapterTool wfa-parity-verify --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tautcony/ChapterTool.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/wfa-parity-verify .agents/skills/wfa-parity-verify && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "wfa-parity-verify" agent skill from https://github.com/tautcony/ChapterTool/tree/master/.codex/skills/wfa-parity-verify into .agents/skills/wfa-parity-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wfa-parity-verify", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tautcony/ChapterTool --skill wfa-parity-verify -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tautcony/ChapterTool wfa-parity-verify --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tautcony/ChapterTool.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/wfa-parity-verify .cursor/skills/wfa-parity-verify && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "wfa-parity-verify" agent skill from https://github.com/tautcony/ChapterTool/tree/master/.codex/skills/wfa-parity-verify into .cursor/skills/wfa-parity-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wfa-parity-verify", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/tautcony/ChapterTool.git --path .codex/skills/wfa-parity-verify--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add tautcony/ChapterTool --skill wfa-parity-verify -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tautcony/ChapterTool wfa-parity-verify --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tautcony/ChapterTool.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/wfa-parity-verify .gemini/skills/wfa-parity-verify && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "wfa-parity-verify" agent skill from https://github.com/tautcony/ChapterTool/tree/master/.codex/skills/wfa-parity-verify into .gemini/skills/wfa-parity-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wfa-parity-verify", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install tautcony/ChapterTool wfa-parity-verifyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add tautcony/ChapterTool --skill wfa-parity-verify -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/tautcony/ChapterTool.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/wfa-parity-verify .github/skills/wfa-parity-verify && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "wfa-parity-verify" agent skill from https://github.com/tautcony/ChapterTool/tree/master/.codex/skills/wfa-parity-verify into .github/skills/wfa-parity-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wfa-parity-verify", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tautcony/ChapterTool --skill wfa-parity-verify -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install tautcony/ChapterTool wfa-parity-verify --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tautcony/ChapterTool.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/wfa-parity-verify .opencode/skills/wfa-parity-verify && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "wfa-parity-verify" agent skill from https://github.com/tautcony/ChapterTool/tree/master/.codex/skills/wfa-parity-verify into .opencode/skills/wfa-parity-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wfa-parity-verify", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
wfa-parity-verify- GitHub stars
- 113
- Token cost
- ~749 tokens
- SKILL.md length
- 295 words
- Files
- 4 (incl. references)
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Phase E of a WinForms-to-Avalonia migration: verify behavioral parity against Phase A contracts, record intentional differences, validate supported environments and packaging, and make…
- Works in 7 steps: Capability matrix → Automated verification → Acceptance checklist → …
- SKILL.md covers Workflow, Deliverables and After E
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Wfa Parity Verify is an agent skill from tautcony/ChapterTool. Phase E of a WinForms-to-Avalonia migration: verify behavioral parity against Phase A contracts, record intentional differences, validate supported environments and packaging, and make evidence-based legacy cutover decisions. Use only for an explicit migration when comparing the legacy and Avalonia implementations or when the orchestrator routes here. Do not delete legacy without the cutover checklist and explicit authorization.
Its SKILL.md is about 750 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/acceptance.md`, `references/cutover-checklist.md` and `references/legacy-diff.md`).
It works with Avalonia. The repository describes itself as: Cross-platform chapter editing and conversion toolkit for desktop, CLI, WebAssembly, and Node.js, with support for Blu-ray and common media chapter formats. The licence is GPL-3.0.
Example prompts
- “/wfa-parity-verify”
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit a66d7ce. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Wfa Parity Verify loads about 749 tokens when it runs, and up to ~1.6k if it reads all its reference files. Until then it costs about 113 tokens; SKILL.md has 295 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from tautcony/ChapterTool at commit a66d7ce, republished under its GPL-3.0 licence (© tautcony). 295 words, ~749 tokens.
Download SKILL.mdSave it as
.claude/skills/wfa-parity-verify/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- wfa-parity-verify
- description
- Phase E of a WinForms-to-Avalonia migration: verify behavioral parity against Phase A contracts, record intentional differences, validate supported environments and packaging, and make evidence-based legacy cutover decisions. Use only for an explicit migration when comparing the legacy and Avalonia implementations or when the orchestrator routes here. Do not delete legacy without the cutover checklist and explicit authorization.
Phase E — Parity verification and cutover
Prove the Avalonia line is the maintenance trunk, document gaps, then freeze or delete legacy only with evidence.
Read acceptance to build repository-specific scenarios, legacy diff to record evidence, and cutover checklist before freezing or deleting legacy code.
Workflow
1. Capability matrix
| Feature | New status | Diff / gap | Impact | Decision (fix/defer/retire) |
Populate the matrix from Phase A. Cover every user command, state transition, external effect, failure/recovery path, accessibility contract, supported environment, and deployment path that the product actually has.
2. Automated verification
Run solution and layer-focused tests; record commands. Sequential multi-project runs if needed.
For large multi-module parity audits, use independent read-only sub-agents per module so conclusions do not pollute one context.
3. Acceptance checklist
Run the Phase A acceptance scenarios against both implementations where possible. Include startup/lifecycle, primary and secondary workflows, invalid input, cancellation, dependency failure, stale-state prevention, accessibility, and recovery.
4. Modernization pass
If still WinForms-shaped (Refresh, no composition root), file and fix high-severity items.
5. Packaging
For each supported target, verify build, publish, install/launch, upgrade or replacement policy, runtime dependencies, assets, licenses, and rollback/recovery expectations.
6. Cutover stages
- Trunk switch — all new work on Avalonia/
src - Legacy freeze — reference only
- Gap burn-down or waivers
- Physical delete only after checklist
“Main path works” is not enough when any required capability or environment remains unverified.
7. Spec verification method
Per capability: implementation status plus automated/manual evidence. Do not mark done when only empty entry points exist. Treat missing untrusted-input bounds, durable persistence, or supported-environment smoke evidence as cutover blockers unless explicitly waived.
Deliverables
- Parity/diff report with decisions
- Test results summary
- Acceptance notes
- Packaging note
- Cutover checklist or dated deferrals
After E
First migration done ≠ product complete. Continue with:
wfa-post-port-evolvefor product upgradeswfa-harden-decomposefor structure/security debt
© tautcony, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (references) in .codex/skills/wfa-parity-verify of tautcony/ChapterTool.
- SKILL.md
- references/acceptance.md
- references/cutover-checklist.md
- references/legacy-diff.md
Open the folder on GitHubat commit a66d7ce
Compare with similar skills
Wfa Parity Verify next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Wfa Parity Verify this skilltautcony/ChapterTool | 113 | — | ~749 | Automated safety check: Pass | GPL-3.0 | |
| Translation Source SyncDevolutions/UniGetUI | 26k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Docs Style LintAvaloniaUI/avalonia-docs | 166 | — | ~4.6k | Automated safety check: Pass | None | |
| Format StylePixeval/Pixeval | 3.2k | — | ~1.2k | Automated safety check: Pass | GPL-3.0 | |
| Docusaurus StylingAvaloniaUI/avalonia-docs | 166 | — | ~3.3k | Automated safety check: Pass | None | |
| Code StylePixeval/Pixeval | 3.2k | — | ~730 | Automated safety check: Pass | GPL-3.0 |
Similar skills
Docs Style Lint
AvaloniaUI/avalonia-docs
Reviews and lints Avalonia documentation pages against house style rules, content boundaries, anti-marketing standards, accessibility, and SEO.
Format Style
Pixeval/Pixeval
工程代码格式化风格指引
Docusaurus Styling
AvaloniaUI/avalonia-docs
Style Docusaurus sites to match Avalonia Customer Portal theme using TailwindCSS, CSS variables, and component swizzling.
Code Style
Pixeval/Pixeval
工程代码编写风格指引（不含简单的格式化风格）
Atomui Resource Lifecycle
AtomUI/AtomUI
A skill your agent uses when changing AtomUI or Avalonia resource bindings, DynamicResource, TokenResourceBinder, non-Visual AvaloniaObject lifecycle, IResourceHost/IThemeVariantHost…
More from tautcony/ChapterTool
All 9 skills in this repoReclaim Code Entropy
tautcony/ChapterTool
Find, rank, and safely remove accidental codebase complexity by proving real consumers, dynamic entrypoints, compatibility obligations, duplicate representations, speculative surfaces, and lifecycle…
Wfa Harden Decompose
tautcony/ChapterTool
Phase G of a WinForms-to-Avalonia migration: decompose oversized UI state and orchestration, harden asynchronous workflows and external boundaries, preserve composition lifetimes, keep Headless…
Wfa Post Port Evolve
tautcony/ChapterTool
Phase F of a WinForms-to-Avalonia migration: evolve the Avalonia trunk after cutover without reintroducing WinForms coupling or bypassing established layers.
Winforms To Avalonia
tautcony/ChapterTool
Orchestrate a phased WinForms-to-Avalonia migration: behavior contracts, UI-independent application logic, platform adapters, MVVM shell, parity/cutover, evolution, and hardening.
Wfa Avalonia UI
tautcony/ChapterTool
Phase D of a WinForms-to-Avalonia migration: build the Avalonia UI shell with composition, MVVM state and commands, responsive XAML, accessibility, localization boundaries, and behavior-focused…
Wfa Capture Contracts
tautcony/ChapterTool
Phase A of a WinForms-to-Avalonia migration: inventory the legacy application, split responsibilities, capture command and state contracts, build a coverage matrix, and define acceptance evidence…
Related
Works with
Questions about Wfa Parity Verify
What does Wfa Parity Verify do?
Phase E of a WinForms-to-Avalonia migration: verify behavioral parity against Phase A contracts, record intentional differences, validate supported environments and packaging, and make…. Wfa Parity Verify is an agent skill from tautcony/ChapterTool. Phase E of a WinForms-to-Avalonia migration: verify behavioral parity against Phase A contracts, record intentional differences, validate supported environments and packaging, and make evidence-based legacy cutover decisions.
How do I install Wfa Parity Verify in Claude Code?
Run `npx skills add tautcony/ChapterTool --skill wfa-parity-verify -a claude-code`. Or copy the skill folder (.codex/skills/wfa-parity-verify in tautcony/ChapterTool) into .claude/skills/wfa-parity-verify in your project. Claude Code loads it when a task matches its description.
How do I install Wfa Parity Verify in Codex?
Run `npx skills add tautcony/ChapterTool --skill wfa-parity-verify -a codex`. Or copy the skill folder (.codex/skills/wfa-parity-verify in tautcony/ChapterTool) into .agents/skills/wfa-parity-verify in your project. Codex loads it when a task matches its description.
Can I use Wfa Parity Verify in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tautcony/ChapterTool --skill wfa-parity-verify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wfa-parity-verify, .gemini/skills/wfa-parity-verify, .github/skills/wfa-parity-verify and .opencode/skills/wfa-parity-verify in your project.
What does Wfa Parity Verify need to run?
SKILL.md names no scripts, command-line tools or credentials: Wfa Parity Verify is instructions for the agent only.
Does Wfa Parity Verify access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Wfa Parity Verify safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Wfa Parity Verify use?
Wfa Parity Verify is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Wfa Parity Verify use?
About 749 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 884 tokens, read only when the agent opens those files.
What are the alternatives to Wfa Parity Verify?
Skills that share tags, products or a category with Wfa Parity Verify: Translation Source Sync (Devolutions/UniGetUI, 26k stars), Docs Style Lint (AvaloniaUI/avalonia-docs, 166 stars), Format Style (Pixeval/Pixeval, 3.2k stars) and Docusaurus Styling (AvaloniaUI/avalonia-docs, 166 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Wfa Parity Verify?
tautcony (a GitHub user) maintains it in tautcony/ChapterTool, which has 113 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 10, 2026.
Source: tautcony/ChapterTool on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.