refine-git-issue

To improve GitHub issue clarity, you can refine bug reports by identifying missing reproduction steps, expected versus actual behavior, scope, and affected files. This ensures incomplete issue descriptions become actionable for development by adding necessary clarifying questions and assumptions.

The best way to identify missing reproduction steps in a GitHub issue is to analyze the bug report for gaps in expected versus actual behavior and scope. The refinement process pinpoints missing information and verifies code paths using ripgrep when possible.

You can rewrite incomplete GitHub bug reports by enhancing the issue text for better understanding and completeness. The process adds necessary questions or assumptions and verifies affected file paths using ripgrep to ensure the bug report is actionable.

Yes, you can use ripgrep to verify affected files mentioned in a GitHub bug report. The issue refinement process verifies code paths with ripgrep when possible to ensure the scope and affected files described in the bug report are accurate.

You need to add clarifying questions to a GitHub issue when a user submits a vague bug report. This happens during issue refinement if the tool identifies missing information like reproduction steps, expected behavior, or affected files before the issue is assigned.

Your GitHub issues may not be actionable for developers due to unclear or incomplete descriptions lacking reproduction steps, expected versus actual behavior, scope, or affected files. Refining the issue text and adding necessary questions or assumptions resolves this lack of clarity.