Scan Repo Discussions

Platforms supported: GitHub

The scan_repo_discussions tool analyzes past PR discussions and metadata to identify recurring feedback patterns, then generates a best_practices.md file with key insights and recommendations.

The best_practices.md file captures patterns specific to your team's workflow, based on real PR discussions. Qodo Merge uses it to give more tailored, context-aware suggestions in future pull requests.

Learn more about the best practices file.

Active repositories are needed

The tool is designed to work with real-life repositories, as it relies on actual discussions to generate meaningful insights.

Notice that at least 50 merged PRs are required to generate a best_practices.md file.

How to use the /scan_repo_discussions tool

Manual usage

Comment on the PR:

/scan_repo_discussions

Qodo Merge will create a new PR that contains an auto-generated best_practices.md file.

Note: Since up to 250 PRs are scanned, the scan could take several minutes to complete.

Configuration options

To force generating a PR with a new best_practices.md file, even if it already exists, use:

/scan_repo_discussions --scan_repo_discussions.force_scan=true

To specify how many days of discussions should be included in the scan, use:

/scan_repo_discussions --scan_repo_discussions.days_back=X # Default is 365

To specify the minimum number of merged PRs needed to generate the best_practices.md file, use:

/scan_repo_discussions --scan_repo_discussions.minimal_number_of_prs=X # Default is 50

Example usage

The PR created by the bot:

The best_practices.md file in the PR: