Format markdown files

hashkode · hashkode · commit 5f301028d463 · 2025-03-26T22:33:31.000+01:00
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -1,32 +1,30 @@
 ---
 name: Bug Report
 about: Create a report to help us improve
-title: '[BUG] '
+title: "[BUG] "
 labels: bug
-assignees: ''
+assignees: ""
 ---
 
-**Describe the bug**
-A clear and concise description of what the bug is.
+**Describe the bug** A clear and concise description of what the bug is.
+
+**To Reproduce** Steps to reproduce the behavior:
 
-**To Reproduce**
-Steps to reproduce the behavior:
 1. Go to '...'
 2. Click on '....'
 3. Scroll down to '....'
 4. See error
 
-**Expected behavior**
-A clear and concise description of what you expected to happen.
+**Expected behavior** A clear and concise description of what you expected to
+happen.
 
-**Screenshots**
-If applicable, add screenshots to help explain your problem.
+**Screenshots** If applicable, add screenshots to help explain your problem.
 
 **Environment (please complete the following information):**
+
 - OS: [e.g. macOS, Windows, Linux]
   - Version [e.g. 1.2.3]
 - Client [if applicable]
   - Version [e.g. 1.2.3]
 
-**Additional context**
-Add any other context about the problem here. 
+**Additional context** Add any other context about the problem here.
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -1,19 +1,19 @@
 ---
 name: Feature Request
 about: Suggest an idea for this project
-title: '[FEATURE] '
+title: "[FEATURE] "
 labels: enhancement
-assignees: ''
+assignees: ""
 ---
 
-**Is your feature request related to a problem? Please describe.**
-A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+**Is your feature request related to a problem? Please describe.** A clear and
+concise description of what the problem is. Ex. I'm always frustrated when [...]
 
-**Describe the solution you'd like**
-A clear and concise description of what you want to happen.
+**Describe the solution you'd like** A clear and concise description of what you
+want to happen.
 
-**Describe alternatives you've considered**
-A clear and concise description of any alternative solutions or features you've considered.
+**Describe alternatives you've considered** A clear and concise description of
+any alternative solutions or features you've considered.
 
-**Additional context**
-Add any other context or screenshots about the feature request here. 
+**Additional context** Add any other context or screenshots about the feature
+request here.
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
@@ -1,24 +1,31 @@
 ## Description
-Please include a summary of the changes and which issue is fixed. Please also include relevant motivation and context.
+
+Please include a summary of the changes and which issue is fixed. Please also
+include relevant motivation and context.
 
 Fixes # (issue)
 
 ## Type of change
+
 Please delete options that are not relevant.
 
 - [ ] Bug fix (non-breaking change which fixes an issue)
 - [ ] New feature (non-breaking change which adds functionality)
-- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] Breaking change (fix or feature that would cause existing functionality to
+      not work as expected)
 - [ ] Documentation update
 
 ## How Has This Been Tested?
-Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
+
+Please describe the tests that you ran to verify your changes. Provide
+instructions so we can reproduce.
 
 ## Checklist:
+
 - [ ] My code follows the style guidelines of this project
 - [ ] I have performed a self-review of my code
 - [ ] I have commented my code, particularly in hard-to-understand areas
 - [ ] I have made corresponding changes to the documentation
 - [ ] My changes generate no new warnings
 - [ ] I have added tests that prove my fix is effective or that my feature works
-- [ ] New and existing unit tests pass locally with my changes (if applicable)
+- [ ] New and existing unit tests pass locally with my changes (if applicable)
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
@@ -17,23 +17,23 @@ diverse, inclusive, and healthy community.
 Examples of behavior that contributes to a positive environment for our
 community include:
 
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes,
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
   and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the overall
+- Focusing on what is best not just for us as individuals, but for the overall
   community
 
 Examples of unacceptable behavior include:
 
-* The use of sexualized language or imagery, and sexual attention or advances of
+- The use of sexualized language or imagery, and sexual attention or advances of
   any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email address,
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address,
   without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
+- Other conduct which could reasonably be considered inappropriate in a
   professional setting
 
 ## Enforcement Responsibilities
@@ -59,9 +59,9 @@ representative at an online or offline event.
 ## Enforcement
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement at
-[info at cobrowser.xyz].
-All complaints will be reviewed and investigated promptly and fairly.
+reported to the community leaders responsible for enforcement at [info at
+cobrowser.xyz]. All complaints will be reviewed and investigated promptly and
+fairly.
 
 All community leaders are obligated to respect the privacy and security of the
 reporter of any incident.
@@ -118,8 +118,8 @@ This Code of Conduct is adapted from the [Contributor Covenant][homepage],
 version 2.1, available at
 [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
 
-Community Impact Guidelines were inspired by
-[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder][Mozilla CoC].
 
 For answers to common questions about this code of conduct, see the FAQ at
 [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -1,6 +1,8 @@
 # Contributing to browser-use MCP Server
 
-First off, thank you for considering contributing to browser-use MCP Server! This project is released under the MIT License, which means your contributions will also be covered under the same permissive license.
+First off, thank you for considering contributing to browser-use MCP Server!
+This project is released under the MIT License, which means your contributions
+will also be covered under the same permissive license.
 
 ### Table of Contents
 
@@ -16,26 +18,33 @@ First off, thank you for considering contributing to browser-use MCP Server! Thi
 
 ## Code of Conduct
 
-We have adopted a Code of Conduct that we expect project participants to adhere to. Please read [the full text](CODE_OF_CONDUCT.md) so that you can understand what actions will and will not be tolerated.
+We have adopted a Code of Conduct that we expect project participants to adhere
+to. Please read [the full text](CODE_OF_CONDUCT.md) so that you can understand
+what actions will and will not be tolerated.
 
 ## Getting Started
 
 ### Fork-based workflow (recommended as a playground)
+
 1. Fork the repository
-2. Clone your fork: `git clone https://github.com/your-username/browser-use-mcp-server.git`
+2. Clone your fork:
+   `git clone https://github.com/your-username/browser-use-mcp-server.git`
 3. Create a new branch: `git checkout -b feature/your-feature-name`
 4. Make your changes
 5. Push to your fork: `git push origin feature/your-feature-name`
 6. Open a Pull Request
 
 ### Direct repository workflow (for contributors)
-1. Clone the repository directly: `git clone https://github.com/co-browser/browser-use-mcp-server.git`
+
+1. Clone the repository directly:
+   `git clone https://github.com/co-browser/browser-use-mcp-server.git`
 2. Create a new branch: `git checkout -b feature/your-feature-name`
 3. Make your changes
 4. Push to the repository: `git push origin feature/your-feature-name`
 5. Open a Pull Request
 
-If you're interested in being contributor, please reach out to the maintainers after making a few successful contributions via issues and pull requests.
+If you're interested in being contributor, please reach out to the maintainers
+after making a few successful contributions via issues and pull requests.
 
 ## How to Contribute
 
@@ -49,14 +58,19 @@ issue noting these corrections, and we'll batch them into larger updates.
 
 We use GitHub issues to track bugs. Before creating a bug report:
 
-- Search existing [Issues](https://github.com/co-browser/browser-use-mcp-server/issues) to ensure it hasn't already been reported
-- If you find a closed issue that seems to address your problem, open a new issue and include a link to the original
+- Search existing
+  [Issues](https://github.com/co-browser/browser-use-mcp-server/issues) to
+  ensure it hasn't already been reported
+- If you find a closed issue that seems to address your problem, open a new
+  issue and include a link to the original
 
-When submitting a bug report, please use our bug report template and include as much detail as possible.
+When submitting a bug report, please use our bug report template and include as
+much detail as possible.
 
 ### Suggesting Enhancements
 
-Enhancement suggestions are tracked through GitHub issues. Please use our feature request template when suggesting enhancements.
+Enhancement suggestions are tracked through GitHub issues. Please use our
+feature request template when suggesting enhancements.
 
 ### Pull Requests
 
@@ -81,4 +95,5 @@ Enhancement suggestions are tracked through GitHub issues. Please use our featur
 
 ## License
 
-By contributing to browser-use MCP Server, you agree that your contributions will be licensed under the MIT License. See [LICENSE](LICENSE) for details.
+By contributing to browser-use MCP Server, you agree that your contributions
+will be licensed under the MIT License. See [LICENSE](LICENSE) for details.
