fix-issue

Resolve GitHub issues end-to-end with investigation, implementation, test verification, and pull request merging.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the entire process of fixing a GitHub issue, from initial investigation and code changes to creating a pull request and merging it.

Core Features & Use Cases

  • Comprehensive Issue Fixing: Handles investigation, root cause analysis, implementation, verification, and PR management.
  • Adherence to Conventions: Ensures all fixes follow project-specific coding and versioning standards.
  • Use Case: When a bug is reported on GitHub, this Skill can be invoked to automatically diagnose the problem, implement a solution, and submit it for review, significantly speeding up the development cycle.

Quick Start

Use the fix-issue skill to fix GitHub issue number 123.

Frequently Asked Questions about fix-issue

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

FAQPage Schema
How do I automate fixing a GitHub issue end to end?

Automating GitHub issue resolution involves fetching the issue, investigating the root cause, implementing code changes, verifying with tests, and creating a pull request. This Skill executes that entire workflow while adhering to project conventions for code quality and versioning.

Can I automatically create and merge pull requests for bug fixes?

Yes, automated pull request creation and merging for bug fixes is supported. After implementing and verifying the code changes via test suites, the workflow handles versioned PR creation and merges it directly within your development pipeline.

What is the best way to ensure automated code changes follow project conventions?

To ensure automated code changes follow project conventions, the resolution process strictly adheres to your repository's established standards for code quality, versioning, and changelog updates throughout the implementation and pull request creation phases.

How does automated root cause investigation work for GitHub bugs?

Automated root cause investigation for GitHub bugs works by fetching the specific issue details and analyzing the codebase to diagnose the problem. It then implements a targeted solution and verifies the fix using test suites before submitting a PR.

Do I need to run test suites separately after automated issue resolution?

No, you do not need to run test suites separately. The automated issue resolution process includes verification via test suites as a built-in step before proceeding to versioned pull request creation and merging.