work

Automate GitHub issue triage, branch creation, TDD implementation, and PR generation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/fwojciec/quiver --skill work-fwojciec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work
Source: https://github.com/fwojciec/quiver/tree/main/.claude/skills/work
Command: npx skills add https://github.com/fwojciec/quiver --skill work-fwojciec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pick GitHub issues, create a feature branch, implement using TDD, review, and create a PR in an automated workflow.

Core Features & Use Cases

  • End-to-end issue workflow: automatically select an issue, spin up a branch, implement via TDD, run tests, seek reviews, and open a PR.
  • Minimal user interaction: prompts only for missing context such as issue number selection or branch naming.
  • Use Case: For a team handling multiple issues, this skill accelerates the cycle from issue to merged PR with consistent branch naming and validation steps.

Quick Start

Start the workflow by providing an issue number and run the skill to automatically set up a branch, implement, review, and create a PR.

Frequently Asked Questions about work

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

FAQPage Schema
How do I automate the GitHub issue to pull request workflow end-to-end?

Automating the GitHub issue to PR workflow involves selecting an issue, creating a feature branch, implementing via TDD, running tests, and generating a PR. This skill orchestrates that entire cycle with minimal user interaction, prompting only for missing context like issue numbers or branch names.

Can I use test-driven development to implement GitHub issues automatically?

Yes, test-driven development is integrated into the implementation phase of the issue resolution workflow. The skill applies a TDD-based approach using a dedicated subskill to write tests and implement code before automatically seeking reviews and opening a pull request.

What do I need to set up automated branch creation and PR generation for GitHub issues?

You need a development environment with Git, the GitHub CLI (gh), and Make installed. These tools enable the skill to automatically create branches, run validation steps, and generate pull requests across multiple repositories.

Does this GitHub issue workflow tool work across multiple repositories?

Yes, the automated GitHub issue workflow is designed for software teams handling issues across multiple repositories. It standardizes the cycle from issue triage to merged PR with consistent branch naming and validation steps.

What is the best way to handle GitHub issue triage to PR with minimal interaction?

The best way to handle issue triage to PR with minimal interaction is using an automated workflow that selects an issue, spins up a branch, implements via TDD, runs tests, seeks reviews, and opens a PR. It prompts only for missing context such as issue selection or branch naming.

Why does automated branch creation require the GitHub CLI and Make?

Automated branch creation requires the GitHub CLI (gh) and Make because the workflow relies on them to interact with GitHub repositories and orchestrate the build and validation steps defined in the skill's workflow configuration.