Docs, for Moxie Docs
DocumentationGuides
  • Account and email preferences
  • Activate and index a repo
  • Changelog from PRs
  • Changelog timeline and overrides
  • Delete your account and feedback
  • Docs Home and collections
  • Drift detection and PR automation
  • Friday Recap and weekly updates
  • Give feedback on answers
  • Manage subscription
  • Publish knowledge base
  • Review drift cards and open focused doc PRs
  • Set up your public knowledgebase
  • Set your collection preferences
  • Tune repository automation settings
  • Use code previews and search helpers
  • Use Friday Recap and Cleanup
  • Workspace onboarding and invitations
  • Admin blog via SnowSEO webhook
  • Billing, trial, or access issues
  • Configure PR automation and detectors
  • Integration: connect an MCP-capable agent
  • Integration: MCP agents
  • Opportunity cards seem noisy or wrong
  • Q&A answers seem wrong or outdated
  • Share changelog to Slack
  • Stripe billing setup and syncing
  • Troubleshoot GitHub App and repository access
  • Troubleshoot GitHub connection and indexing
  • Troubleshoot GitHub PRs
  • Troubleshoot indexing
HomeDocumentationTune repository automation settings

Tune repository automation settings

2 min read•Updated Sep 20, 2026

Overview

Use repository automation to keep docs in step with code. Moxie Docs shows opportunity cards when documentation falls behind, and lets you open focused doc pull requests (PRs) right from the dashboard. You can also dismiss or mute individual findings to reduce noise, and admins can enable or disable specific detectors per repository to shape what appears.

When to use it

  • You see drift between code changes and docs and want quick, focused updates.
  • Your team needs fewer noisy alerts and more relevant suggestions.
  • You want to review and merge proposed doc PRs from one place.
  • You need to temporarily silence a finding while work is in progress.

How to use it

  1. Open the Docs dashboard and go to the repository you want to review.
  2. Review opportunity cards that flag where docs may have fallen behind code.
  3. Open a focused doc PR from a card to see the proposed changes in GitHub.
  4. Review and edit the proposed PR as needed, then merge it in GitHub when ready.
  5. If a card is not useful, click its overflow menu and choose Dismiss to remove it.
  6. To reduce short-term noise, click the overflow menu and choose Mute 7d or Mute 30d to pause that finding for the selected period.
  7. If you are an admin and want to change what gets flagged, open repository automation settings and adjust Detectors for that repository by enabling or disabling specific detectors.
  8. Return to the dashboard to confirm that only relevant opportunity cards appear going forward.

Admin: tune detectors per repository

  1. Open account settings and go to the repository’s automation controls.
  2. Select the Repository automation tab.
  3. Open Detectors and enable or disable the specific detectors you want active for this repository.
  4. Save your changes and refresh the Docs dashboard to see updated opportunity cards over time.

Options and settings

  • Overflow menu on opportunity cards: Dismiss, Mute 7d, Mute 30d.
  • Detectors (per repository, admin only): Enable or disable individual drift detectors to shape which opportunity cards appear.

Tips

  • Use Dismiss when a finding is not relevant; use Mute when it is valid but not actionable yet.
  • Start with a smaller set of detectors and add more once your team is comfortable with the volume.
  • After merging a focused doc PR, give the system a moment to update and clear the corresponding card.
  • Detector changes affect future cards; existing muted or dismissed items keep their current state.

Was this page helpful?

Let us know if you found what you were looking for.

Related articles

DocumentationAccount and email preferencesUse Account settings to control which product emails Moxie Docs sends you, and to permanen
DocumentationActivate and index a repoActivate Docs to turn a connected GitHub repository into an organized, searchable knowledg
DocumentationChangelog from PRsChangelog from PRs builds a shareable release or sprint changelog from your merged GitHub
PreviousSet your collection preferences
Next Use code previews and search helpers

On this page

  • Overview
  • When to use it
  • How to use it
  • Admin: tune detectors per repository
  • Options and settings
  • Tips
Changelogllms.txt

Powered by Moxie Docs

Overview

Use repository automation to keep docs in step with code. Moxie Docs shows opportunity cards when documentation falls behind, and lets you open focused doc pull requests (PRs) right from the dashboard. You can also dismiss or mute individual findings to reduce noise, and admins can enable or disable specific detectors per repository to shape what appears.

When to use it

  • You see drift between code changes and docs and want quick, focused updates.
  • Your team needs fewer noisy alerts and more relevant suggestions.
  • You want to review and merge proposed doc PRs from one place.
  • You need to temporarily silence a finding while work is in progress.

How to use it

  1. Open the Docs dashboard and go to the repository you want to review.
  2. Review opportunity cards that flag where docs may have fallen behind code.
  3. Open a focused doc PR from a card to see the proposed changes in GitHub.
  4. Review and edit the proposed PR as needed, then merge it in GitHub when ready.
  5. If a card is not useful, click its overflow menu and choose Dismiss to remove it.
  6. To reduce short-term noise, click the overflow menu and choose Mute 7d or Mute 30d to pause that finding for the selected period.
  7. If you are an admin and want to change what gets flagged, open repository automation settings and adjust Detectors for that repository by enabling or disabling specific detectors.
  8. Return to the dashboard to confirm that only relevant opportunity cards appear going forward.

Admin: tune detectors per repository

  1. Open account settings and go to the repository’s automation controls.
  2. Select the Repository automation tab.
  3. Open Detectors and enable or disable the specific detectors you want active for this repository.
  4. Save your changes and refresh the Docs dashboard to see updated opportunity cards over time.

Options and settings

  • Overflow menu on opportunity cards: Dismiss, Mute 7d, Mute 30d.
  • Detectors (per repository, admin only): Enable or disable individual drift detectors to shape which opportunity cards appear.

Tips

  • Use Dismiss when a finding is not relevant; use Mute when it is valid but not actionable yet.
  • Start with a smaller set of detectors and add more once your team is comfortable with the volume.
  • After merging a focused doc PR, give the system a moment to update and clear the corresponding card.
  • Detector changes affect future cards; existing muted or dismissed items keep their current state.