ez-workflow

Standardize stacked pull request workflows for AI agents using ez-stack commands.

23|4|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/rohoswagger/ez-stack --skill ez-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ez-workflow
Source: https://github.com/rohoswagger/ez-stack/tree/main
Command: npx skills add https://github.com/rohoswagger/ez-stack --skill ez-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ez-workflow reduces friction and mistakes when AI agents need to create branches, commit changes, push updates, and manage stacked pull requests in a repo already controlled by ez-stack.

Core Features & Use Cases

  • Agent-safe branch lifecycle: Guides agents to use ez create for worktree isolation and correct stacking semantics instead of raw git/gh commands.
  • Deterministic, validated mutation flow: Encourages preferred commit/push/sync commands and explains when to use stage-all vs staged-file commits, including scope checks and receipts.
  • Multi-agent collaboration and PR hygiene: Shows how to keep stacks consistent via ez sync/restack and how to finish branch cleanup with ez delete.

Quick Start

Use the ez-workflow instructions to manage a new change by first switching into an isolated worktree using cd $(ez create my-task --from main).

Frequently Asked Questions about ez-workflow

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

FAQPage Schema
How do I manage stacked pull requests with AI agents without using raw git commands?

Standardize stacked pull request workflows by enforcing ez-managed operations like create, commit, and push instead of raw git checkout or gh pr create. This applies branch creation, committing, and safe multi-agent collaboration across worktrees.

What is the best way to isolate AI agent changes in git worktrees?

Isolate AI agent changes by switching into a dedicated worktree using the ez create command with a task name and base branch. This ensures correct stacking semantics and prevents interference during multi-agent collaboration.

How does syncing and restacking work for multi-agent git workflows?

Syncing and restacking in multi-agent git workflows keeps stacked branches consistent using ez sync and restack commands. This validates mutations through receipts and ensures PR hygiene across isolated worktrees without manual rebasing.

Can I commit staged files individually in a stacked PR workflow?

Yes, the stacked PR workflow supports both stage-all and staged-file commits. It guides agents on when to use scoped updates and staged-path commits, applying scope checks and receipts-based verification before pushing.

Why should I avoid raw git checkout and commit for AI agent workflows?

Avoiding raw git checkout and commit prevents friction and mistakes in repositories managed by ez-stack. Enforcing ez-managed operations ensures deterministic, validated mutation flows and correct stacking semantics for AI agents.

Do I need ez-stack to manage stacked pull requests for AI agents?

Yes, ez-workflow applies to repositories already controlled by ez-stack. It requires enforcing ez-managed operations for branch creation, committing, pushing, syncing, and deletion to maintain safe multi-agent collaboration.