skills.rest
dlepaux
dlepauxCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

fix-issue

Convert backlog stories into pull requests with automated quality gates.

Updated Aug 23, 2026
Search Tags:#automation#branching#plan#lint#quality-gates#pull-request#tests
One-click install
npx skills add https://github.com/dlepaux/dotfiles --skill fix-issue-dlepaux
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix-issue
Source: https://github.com/dlepaux/dotfiles/tree/main/.claude/skills/fix-issue
Command: npx skills add https://github.com/dlepaux/dotfiles --skill fix-issue-dlepaux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manages turning a backlog story into a production-ready PR by reading plan/index and/or GitHub issues, applying automated quality gates (tests, linting, type checks), and creating a PR with proper traceability.

Core Features & Use Cases

  • Automatically locate a story from plan/ or a linked GitHub issue and derive the work to implement.
  • Create a branch named from the story slug, run tests and checks, and open a PR with a concise summary of changes.
  • Update plan statuses and reference the PR in the story to maintain traceability across the product backlog.

Quick Start

Provide a plan path or GitHub issue number, and the skill will generate a branch, run checks, and open a PR.

Frequently Asked Questions about fix-issue

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

FAQPage Schema
How do I automate creating a pull request from a backlog story?▼

To automate creating a pull request from a backlog story, provide a plan path or GitHub issue number. The system reads the plan, creates a branch, runs quality gates like tests and linting, and opens a PR with traceability.

What quality gates are validated before a pull request is completed?▼

Quality gates validated before a pull request is completed include automated tests, linting, type checks, and code review criteria. The system ensures these checks pass to maintain code quality before finalizing the PR.

Do I need GitHub access tokens to automate branch creation and PR generation?▼

GitHub access tokens are required if you are reading linked GitHub issues and automating PR generation. Alternatively, you can use a project configured with local plan folders to derive the work without direct GitHub access.

How does automating pull requests maintain traceability across the product backlog?▼

Automating pull requests maintains traceability by updating plan statuses and referencing the newly opened PR directly within the story. This links the backlog item to the production-ready code changes for continuous tracking.

Can I use a linked GitHub issue to generate a branch and run lint checks?▼

Yes, you can use a linked GitHub issue to generate a branch and run lint checks. The system locates the issue, derives the implementation work, creates a slug-named branch, and applies automated quality gates before opening a PR.

What happens if tests or type checks fail during automated PR generation?▼

If tests or type checks fail during automated PR generation, the quality gates prevent the pull request from completing. The system validates tests, linting, types, and code review criteria to ensure only passing code generates a PR.

Related Skills

Explore More Product & Management Skills→
Eric-Pacheco95Eric-Pacheco95

sprint-planning

Generate a Markdown sprint plan with committed and stretch stories and risks.

Community
Advanced
mrgeoffrichmrgeoffrich
3

ship-it

Merge reviewed GitHub pull requests and update issue statuses.

Community
Intermediate
acta0724acta0724

verification-loop

Automates multi-phase code quality verification including builds, linting, and testing before pull request creation.

Community
Intermediate
cwijayasundaracwijayasundara
3

gate

Execute pre-merge quality gate checks with automated code reviews and security checks.

Community
Advanced