`/issues`

Description

The /issues command in Qodo Gen is engineered to enhance code quality and security by identifying potential issues within your codebase. Available in Git-Diff Focus, this command scrutinizes your code for a variety of issues, such as security vulnerabilities, logical errors, debugging remnants, and more. Each identified issue is accompanied by a tag indicating its type, a direct link to the implicated code, and a detailed description of the problem. This feature is essential for preemptively addressing problems that could compromise your project's integrity or performance.

How to Use

Follow these steps to efficiently utilize the /issues command:

Select Your Changeset: Identify the scope by selecting file, local, staged, or committed changes.
Select Target Branch (for committed changes): If your focus is on committed changes, you must select the target branch to which your current working branch will be compared. For local or staged changes, proceed directly to initiating the command as these do not require a target branch selection.
Initiate the Command: Type /issues in the chat interface. Qodo Gen then proceeds to analyze the selected scope—either the entire changeset (loca, stages or committed changes) or the specified changes in a file—for potential issues.
Review Identified Issues: Qodo Gen presents a list of found issues, each tagged with its type (e.g., Security Concern, Potential Issue, Leftover Debugging Code, Misspelled Variable). Alongside each issue is a link to the relevant code and a comprehensive description of the problem, enabling you to quickly grasp and locate the concern.
Continue the Chat for Fixes: If you wish to receive suggestions for fixing the identified issues, you can continue the chat directly from the issues list. Ask Qodo Gen for specific advice on how to address each concern. Qodo Gen will provide tailored suggestions for resolving the problems, enhancing the security and quality of your code.

Available in

Git-Diff focus

Example

Command:

/issues