> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qodo.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Review and activate suggested rules
> Learn how Qodo surfaces suggested rules from your codebase and pull request history, and how to review and activate them.
export const AzureIcon = () => ;
BetaGitHubBitbucketAzure DevOps
Suggested rules help you formalize standards that already exist in your codebase and review process. They are not enforced until explicitly reviewed and approved by an admin. Qodo surfaces them as recommendations, giving you visibility into recurring review feedback and best practices, while leaving the decision to review, adjust, and activate each rule in your hands.
## What are suggested rules?
They appear under **Rules > Suggestions** and act as a recommendation layer between informal practices and enforced standards.
Suggested rules help teams:
* Capture repeated review feedback as formal rules
* Align enforcement with real codebase behavior
* Reduce reliance on tribal knowledge and reviewer memory
## What you see in the Suggestions table
Each suggested rule appears as a pending rule in the Suggestions table, along with the key details you need to evaluate it. This information helps you quickly assess context, relevance, and priority before deciding whether to activate the rule.
## Sources of suggestions
Suggested rules are generated from your organization’s pull request history in two ways:
| Source | How it works |
| -------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **[Rule Miner](/governance/rule-enforcement/rule-miner)** | Runs automatically on a schedule. Analyzes PR discussions across your repositories and generates suggested rules continuously as new pull requests are merged. |
| **[User-created rules](/governance/rule-enforcement/generate-and-manage-rules)** | Users (non-admins) can generate rules in the portal. Their rules appear here for admin review before activation, unless an admin has enabled [Auto-approve user suggestions](/install-and-configure/configuration-overview/portal-configuration#review-standards). |
The `/scan_repo_discussions` command has been deprecated and is no longer available. Rule discovery is now handled automatically by [Rule Miner](/governance/rule-enforcement/rule-miner) on a recurring schedule. No manual trigger is required.
## Reviewing and activating suggestions
To review suggested rules:
Go to **Rules > Suggestions.**
Open a suggestion.
Review the rule content, examples, and source.
Set the scope of the rule. See [Rule scope](/governance/rule-enforcement/generate-and-manage-rules#anatomy-of-a-rule) for the available options.
Edit the rule if needed.
Click **Accept & activate** or **Dismiss.**
Suggestions can also be accepted from the **actions menu (â‹®)** in the Suggestions table.
Once accepted, a suggested rule becomes a standard rule and follows the same lifecycle as any other rule.
## Accept or dismiss suggestions in bulk
Select the checkbox next to each suggestion in the Suggestions table, then choose **Accept & activate** or **Dismiss** to process them all at once. To select every suggestion at once, select the checkbox in the table's top row. When you dismiss suggestions, you must confirm the action in a dialog before it is applied.
## Next steps
* [Rule Miner](/governance/rule-enforcement/rule-miner): Understand how suggested rules are generated automatically.
* [Generate and manage rules](/governance/rule-enforcement/generate-and-manage-rules): Create rules manually and manage active rules.
## What are suggested rules?
They appear under **Rules > Suggestions** and act as a recommendation layer between informal practices and enforced standards.
Suggested rules help teams:
* Capture repeated review feedback as formal rules
* Align enforcement with real codebase behavior
* Reduce reliance on tribal knowledge and reviewer memory
## What you see in the Suggestions table
Each suggested rule appears as a pending rule in the Suggestions table, along with the key details you need to evaluate it. This information helps you quickly assess context, relevance, and priority before deciding whether to activate the rule.
## Sources of suggestions
Suggested rules are generated from your organization’s pull request history in two ways:
| Source | How it works |
| -------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **[Rule Miner](/governance/rule-enforcement/rule-miner)** | Runs automatically on a schedule. Analyzes PR discussions across your repositories and generates suggested rules continuously as new pull requests are merged. |
| **[User-created rules](/governance/rule-enforcement/generate-and-manage-rules)** | Users (non-admins) can generate rules in the portal. Their rules appear here for admin review before activation, unless an admin has enabled [Auto-approve user suggestions](/install-and-configure/configuration-overview/portal-configuration#review-standards). |
## Next steps
* [Rule Miner](/governance/rule-enforcement/rule-miner): Understand how suggested rules are generated automatically.
* [Generate and manage rules](/governance/rule-enforcement/generate-and-manage-rules): Create rules manually and manage active rules.