verify-gwm

Verify gwm-rust code changes through builds, command tests, and TUI interactions.

18|Updated Jun 26, 2025
One-click install
npx skills add https://github.com/shutootaki/gwm --skill verify-gwm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-gwm
Source: https://github.com/shutootaki/gwm/tree/main/.claude/skills/verify-gwm
Command: npx skills add https://github.com/shutootaki/gwm --skill verify-gwm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that changes made to the gwm-rust codebase are functioning correctly by performing a series of automated and manual verification steps.

Core Features & Use Cases

  • Build Verification: Confirms the project builds successfully.
  • Command Execution Tests: Validates the behavior of various gwm commands, including help, list, add, go, remove, clean, and pull-main.
  • TUI (Text User Interface) Testing: Checks the visual integrity and interactive functionality of the TUI components.
  • Error Case Handling: Verifies that the tool provides clear and helpful error messages for invalid inputs or scenarios.
  • Use Case: After a developer modifies the gwm CLI tool, this Skill is used to systematically test all functionalities to guarantee no regressions were introduced before merging the changes.

Quick Start

Run the verify-gwm skill to perform a full verification of the gwm-rust code changes.

Frequently Asked Questions about verify-gwm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify Rust CLI tool changes before merging?

To verify Rust CLI tool changes, you can run automated build checks, command execution tests, and TUI interaction tests to ensure functional correctness and robust error handling before merging.

How do I test text user interface components in a Rust application?

You can test text user interface components by executing TUI interaction tests that check the visual integrity and interactive functionality of the command-line interface components.

What is the best way to validate error handling in a CLI tool?

Validating error handling in a CLI tool involves running error case tests to verify that the tool provides clear and helpful error messages for invalid inputs or unexpected scenarios.

Does this verification process support testing Git worktree manager commands?

Yes, the verification process supports testing Git worktree manager commands by validating the behavior of operations like list, add, go, remove, clean, and pull-main.

How to systematically test all command-line operations for regressions?

You systematically test command-line operations for regressions by performing build verification and executing command tests across all available CLI commands to guarantee no issues were introduced.

What are the limitations of automated TUI and command testing?

The limitations of automated TUI and command testing involve ensuring comprehensive coverage of UI/UX improvements and complex interactive operations, requiring robust error handling to manage edge cases effectively.