FixIssue

Automate issue triage, code fixing, and pull request creation across GitHub and GitLab.

3|1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/N4M3Z/forge-dev --skill fixissue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: FixIssue
Source: https://github.com/N4M3Z/forge-dev/tree/main/skills/FixIssue
Command: npx skills add https://github.com/N4M3Z/forge-dev --skill fixissue

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the entire process of fixing software issues, from initial triage and diagnosis to creating pull requests and closing the issue, supporting both GitHub and GitLab platforms.

Core Features & Use Cases

  • Automated Issue Triage: Fetches and parses issue details, checks for existing work, and classifies the fix location.
  • Cross-Platform Support: Works seamlessly with GitHub (using gh) and GitLab (using glab), including cross-repository fixes.
  • Workflow Automation: Automates branch creation, code fixing, testing, submodule bumping, and PR/MR creation.
  • Use Case: When a bug is reported in an issue tracker, this Skill can automatically create a branch, implement the fix in the correct repository, create a pull request, and ensure the issue is closed upon merging.

Quick Start

Use the FixIssue skill to fix issue owner/repo#123.

Frequently Asked Questions about FixIssue

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 from triage to pull request?

To automate fixing a GitHub issue end-to-end, the Skill fetches issue details, creates a branch, implements the code fix, runs tests, and generates a pull request. It uses the gh CLI and automatically closes the issue upon merge using platform-specific keywords.

Can I automate GitLab merge request creation when fixing a reported bug?

Yes, you can automate GitLab merge request creation when fixing a bug. The Skill uses the glab CLI to handle issue triage, branch creation, code modifications, and merge request generation, functioning seamlessly across both GitHub and GitLab platforms.

What is the best way to handle cross-repository dependencies during an automated bug fix?

The best way to handle cross-repository dependencies during an automated bug fix is to use the Skill's cross-repo dependency management. It diagnoses the fix location, bumps submodules as needed, and manually closes issues in external repositories if automated closing is unsupported.

Does this automated issue fixing workflow support both GitHub and GitLab?

Yes, this automated issue fixing workflow supports both GitHub and GitLab. It integrates with the gh and glab CLIs to automate branch creation, code fixing, testing, and pull or merge request generation across both platforms, including cross-repository scenarios.

How does automated issue triage work before creating a branch for a bug fix?

Automated issue triage works by fetching and parsing issue details from the tracker, checking for existing work, and classifying the correct repository for the fix. This diagnosis step ensures the branch creation and code fixing occur in the right location.