winston-wolfe

Creates GitHub pull requests for approved wolfe:queued issues and verifies fixes before merging.

Updated Jun 15, 2026
One-click install
npx skills add https://github.com/jdforsythe/wolfe-pack --skill winston-wolfe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: winston-wolfe
Source: https://github.com/jdforsythe/wolfe-pack/tree/main/templates/bots/winston-wolfe
Command: npx skills add https://github.com/jdforsythe/wolfe-pack --skill winston-wolfe

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of creating Pull Requests from issues labeled with 'wolfe:queued', streamlining the workflow for developers.

Core Features & Use Cases

  • Automated PR Creation: Automatically creates PRs for issues that have been approved by humans.
  • Tests-First Development: Ensures that every fix comes with a failing test and a passing one.
  • No Unverified Output: Ensures that no PR is opened unless it passes a thorough verification process.

Quick Start

Run the command: /winston-wolfe --issue=N

Frequently Asked Questions about winston-wolfe

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

FAQPage Schema
How do I automate pull request creation from GitHub issues?

Automating pull request creation from GitHub issues is done by labeling approved issues with 'wolfe:queued' and running the command to automatically generate a PR for each issue.

How does automated issue automation handle code verification before merging?

Automated issue automation handles code verification by ensuring every fix includes a failing test followed by a passing test, verifying the fix before allowing a human to merge the PR.

Do I need a specific repository configuration to automate PR creation?

You need a valid 'WOLFE.md' index file in your repository to automate PR creation, which allows the process to operate within a restricted autonomy level before human review.

What is the best way to ensure no unverified code is merged from queued issues?

To ensure no unverified code is merged from queued issues, use a tests-first development approach that blocks PR creation unless the fix passes a thorough verification process.

Are there limitations to repository automation when processing queued issues?

Repository automation limitations include requiring human review for merging, depending on internal repository processes, and needing a valid 'WOLFE.md' index to function.