fix-bug

Parse GitHub or YouTrack issues, generate failing tests, and create pull requests.

9.3k|794|Updated Jul 30, 2013
One-click install
npx skills add https://github.com/JetBrains/Exposed --skill fix-bug-jetbrains
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-bug
Source: https://github.com/JetBrains/Exposed/tree/main/.claude/skills/fix-bug
Command: npx skills add https://github.com/JetBrains/Exposed --skill fix-bug-jetbrains

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the entire process of fixing bugs reported in issue trackers, from understanding the issue to creating a pull request with the fix.

Core Features & Use Cases

  • Issue Triage: Parses GitHub and YouTrack issues to gather all necessary details.
  • Reproducer Creation: Automatically writes failing tests to pinpoint the bug.
  • Automated Workflow: Handles branch creation, fixing, validation, and PR generation.
  • Use Case: When a bug is reported on YouTrack (e.g., EXPOSED-1234), this Skill can be invoked to automatically reproduce the bug, implement a fix, and prepare a pull request for review.

Quick Start

Use the fix-bug skill to address GitHub issue #123.

Frequently Asked Questions about fix-bug

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

FAQPage Schema
How do I automate a bug fix workflow from issue creation to pull request?

Automating a bug fix workflow involves parsing issue details from trackers like YouTrack, generating failing reproducer tests, creating a new branch, implementing the fix, validating it, and opening a pull request. This Skill handles this entire process end-to-end.

Can I automatically generate failing tests for GitHub issues before applying a fix?

Yes, automatically generating failing reproducer tests is a core step. The Skill parses the GitHub issue details to understand the bug and then writes a failing test to pinpoint the problem before implementing the actual code fix.

Does this automated bug fixing process require YouTrack integration?

YouTrack integration is required for parsing issue details and updating tracking status. The Skill specifically requires the YouTrack MCP to gather necessary issue information, though it also supports parsing issues directly from GitHub.

How to validate code fixes and check code style during automated bug fixing?

Validating code fixes and checking code style is handled using Gradle. The Skill automates running Gradle tests to validate the implemented solution and ensure code style compliance before creating the pull request.

What is the best way to handle Exposed project bug reports from issue trackers?

The best way to handle Exposed project bug reports is to use an automated workflow that parses the YouTrack or GitHub issue, generates a reproducer test, fixes the code on a new branch, and prepares a pull request for review.

Do I need to manually create branches for automated pull requests?

No, manual branch creation is not needed. The automated workflow handles branch creation automatically, implements the fix, validates the solution using Gradle, and then generates the pull request directly from the new branch.