quickfix

Create a feature branch, run unit tests, and open a PR from dirty main edits.

1|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/zeveck/zskills-dev --skill quickfix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quickfix
Source: https://github.com/zeveck/zskills-dev/tree/main/.claude/skills/quickfix
Command: npx skills add https://github.com/zeveck/zskills-dev --skill quickfix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn in-flight edits on the current main into a ready-to-submit PR without creating a separate worktree, reducing context-switching and overhead.

Core Features & Use Cases

  • In-flight fix → PR without a worktree; preserves dirty main edits for quick shipping.
  • Supports two modes: user-edited (dirty tree + description) and agent-dispatched (clean tree with model-driven edits).
  • Enforces project constraints: unit_cmd alignment, landing == pr, pre-commit checks, and automatic PR creation.

Quick Start

Describe the fix you want shipped, and the Skill will create a feature branch, run unit tests, and open a PR.

Frequently Asked Questions about quickfix

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

FAQPage Schema
How do I turn in-flight edits on a dirty main into a pull request without a worktree?

To turn in-flight edits into a pull request without a worktree, you can use an automated branch management workflow that creates a feature branch, runs unit tests, and opens a PR directly from your dirty main. This preserves your local edits while shipping the fix.

Can I submit a quick code fix as a PR if my local git branch has uncommitted changes?

Yes, you can submit a quick code fix as a PR from a local git branch with uncommitted changes. The workflow supports a user-edited mode that takes your dirty tree and fix description to automatically create a branch and submit the PR.

What is the best way to automate PR creation while enforcing pre-commit hooks and unit tests?

The best way to automate PR creation while enforcing pre-commit hooks and unit tests is using an agent-dispatched workflow. It applies model-driven edits to a clean tree, runs unit command alignments, and enforces pre-commit checks before opening the PR.

Does this automated PR workflow support both manual user edits and agent-dispatched code changes?

Yes, this automated PR workflow supports both manual user edits and agent-dispatched code changes. It handles user-edited mode with a dirty tree and description, alongside an agent-dispatched mode using model-driven edits on a clean tree.

Why should I ship isolated fixes without creating a separate git worktree?

You should ship isolated fixes without creating a separate git worktree to reduce context-switching and overhead. This approach allows rapid, isolated fixes directly from a dirty main, streamlining the code-change workflow for immediate shipping.

When do I need to use a worktree-free approach for branch management and PR creation?

You need a worktree-free approach for branch management and PR creation when your project enforces PR-only landing constraints and requires rapid shipping of in-flight edits. This ensures testing alignment and pre-commit checks without the overhead of worktree setup.