fix: broken doc links

[mds1]

Small PR to fix detector links that didn't work

[coderabbitai]

Walkthrough

The update enriches the Slither tool by refining documentation and functionality for detecting incorrect patterns in assembly code. It focuses on ensuring users have accurate information on identifying incorrect returns and the usage of return instead of leave in assembly blocks.

Changes

File Path	Change Summary
README.md	Semantic changes in detector descriptions for incorrect returns and return-leave.
slither/detectors/assembly/incorrect_return.py	Updated URL in documentation for incorrect return detection.
slither/detectors/assembly/return_instead_of_leave.py	Updated URL for detecting return instead of leave in assembly code.

Poem

🐇✨
In the realm of code, where bugs often hide,
A rabbit hops through, with updates wide.
Assembly fixed, with a doc update,
Ensuring your code's fate is nothing but great.
🌟🐾

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between e3dcf1e and 63d07ae.

Files selected for processing (3)

• README.md (2 hunks)
• slither/detectors/assembly/incorrect_return.py (1 hunks)
• slither/detectors/assembly/return_instead_of_leave.py (1 hunks)

Files skipped from review due to trivial changes (2)

• slither/detectors/assembly/incorrect_return.py
• slither/detectors/assembly/return_instead_of_leave.py

Additional comments: 2

README.md (2)

• 134-134: The link update for the incorrect-return detector is intended to direct users to the correct documentation. Ensure the URL is accessible and points to the relevant documentation page.
• 137-137: Similar to the incorrect-return detector, verify that the updated link for the return-leave detector accurately directs users to the intended documentation, enhancing the usability of the Slither documentation.

[0xalpharush]

Thanks @mds1!