pull-weeds

Convert open weed-labeled issues into gated pull requests using GitHub CLI.

Updated Aug 27, 2026

Search Tags:#automation #github #gate #pull-request #issue-management #weed

Ready to run

npx skills add https://github.com/bketelsen/ytsejam --skill pull-weeds

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pull-weeds
Source: https://github.com/bketelsen/ytsejam/tree/main/contrib/skills/pull-weeds
Command: npx skills add https://github.com/bketelsen/ytsejam --skill pull-weeds

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clear the weed backlog by turning open weed-labeled issues into isolated, gated pull requests. Each issue is addressed with a small, safe fix and each PR must pass a gate before merging.

Core Features & Use Cases

Per-issue dispatch: one gated PR per weed issue.
Isolated worktrees and safe fixes: fixes are contained and reproducible.
Gate-driven workflow: no PR is opened on a failed gate; serialized Phase 2.5 gating after merges.
Workflow references: uses gh, git, and a standard gate script.

Quick Start

Run Phase 1 to collect open weed issues labeled weed, then dispatch isolated fixes for each with a gated PR.

Frequently Asked Questions about pull-weeds

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

FAQPage Schema

How do I automate pull requests for GitHub issues labeled as weeds?▼

Automating pull requests for GitHub weed-labeled issues involves dispatching each issue into an isolated git worktree to create a small fix, then opening a pull request only after it passes a standard gate script.

What is a gated pull request workflow for issue management?▼

A gated pull request workflow requires every generated fix to pass a standard gate script before opening a PR, enforcing safe small fixes and serialized gating after merges to prevent broken code from entering the main branch.

How do I use git worktrees to isolate fixes for multiple GitHub issues?▼

Using git worktrees to isolate fixes creates separate working directories for each weed-labeled issue, ensuring reproducible and contained changes before dispatching individual gated pull requests via GitHub CLI.

Does this automated PR workflow require a specific gate script to run?▼

Yes, the automated PR workflow requires a standard gate script that every change must pass before a pull request is opened, ensuring safe fixes and serialized Phase 2.5 gating after each merge.

What happens to a pull request when the gate script fails during issue automation?▼

When the gate script fails during issue automation, no pull request is opened for that weed-labeled issue, preventing unsafe fixes from reaching the repository until the gate passes.

Can I use GitHub CLI to manage weed issue backlogs and generate safe fixes?▼

Yes, you can use GitHub CLI alongside git and a standard gate script to collect open weed-labeled issues, dispatch isolated worktrees for each, and generate gated pull requests for safe fixes.