gza-test-and-fix

Run verify_command on feature branch changes and commit fixes.

11|1|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/mhawthorne/gza --skill gza-test-and-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gza-test-and-fix
Source: https://github.com/mhawthorne/gza/tree/main/src/gza/skills/gza-test-and-fix
Command: npx skills add https://github.com/mhawthorne/gza --skill gza-test-and-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates detecting failures introduced on a feature branch by running the project's verify_command and automatically applying fixes to files changed on that branch, reducing manual debugging time.

Core Features & Use Cases

  • Automated verification: Run the verify_command and surface failures to the developer.
  • Targeted fixes: Only modify files changed on the current branch to resolve issues.
  • Iterative fixes and commit: Up to three fix iterations are performed, followed by a single commit with all changes.

Quick Start

Run uv run gza config to obtain verify_command, then let the skill automatically fix issues on the current branch.

Frequently Asked Questions about gza-test-and-fix

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

FAQPage Schema
How do I automate running verify_command and fixing failures on a feature branch?

Automated branch verification runs your project's verify_command, targets only files changed on the current branch, and applies fixes automatically. It iterates up to three times before committing all changes in a single commit.

What is needed to configure verify_command for continuous integration fixes?

Configuring verify_command requires defining it in your gza.yaml file. You can obtain this configuration by running the setup command, which enables the skill to proceed with automated fixes.

Can I limit automated code fixes to only files changed on the current git branch?

Yes, automated code fixes are strictly limited to files changed on the current git branch. This targeted approach ensures that only your recent feature branch modifications are adjusted during the verification process.

How many fix iterations are performed before committing automated branch fixes?

Automated branch fixes perform up to three iterations of running verify_command and applying fixes. After these three attempts, all successful modifications are committed together in a single commit.

Why does automated verification fail to proceed on my feature branch?

Automated verification cannot proceed if verify_command is not defined in your gza.yaml file. The skill reports actionable guidance to help you configure the necessary verification steps.

Does this skill work with pre-commit hooks for branch management?

Yes, this skill integrates with pre-commit workflows by automating verification and fixes before committing. It enhances branch management by ensuring feature branch changes pass verify_command before a commit is created.