Add development setup guidelines (#32)

Author: horrormyth

CONTRIBUTION.md

@@ -1,8 +1,10 @@
 ## Contributing Guidelines
+<hr>
 
 Thank you for considering contributing to our project! We welcome contributions from everyone. To maintain a positive and collaborative environment, please follow these guidelines:
 
 ### Creating Issues:
+<hr>
 
 1. **Search Existing Issues**: Before creating a new issue, please search existing issues to see if the topic has already been discussed or reported.
 
@@ -12,7 +14,23 @@ Thank you for considering contributing to our project! We welcome contributions
 
 4. **Use Labels**: Use appropriate labels to categorize your issue (e.g., bug, enhancement, documentation, etc.).
 
+### Development Setup:
+<hr>
+
+1. Fork and clone the Repository
+2. Pull latest changes from the main repository if it has diverged
+3. [Create a virtual environment for the project](https://docs.python.org/3/library/venv.html)
+4. Install dependencies using `pip install -r requirements.txt`
+5. Install pre-commit hook using `pre-commit install`
+6. Run tests using `pytest tests/test_file_name.py ` or specific test name like `pytest tests/test_file_name.py::test_function_name`
+7. Do not push changes without the tests and coverage passing
+8. Commit your changes with **proper** commit messages in imperative form like `Add my best feature`, `Fix issues casusing whatever`, `Update docs` etc: [Good reference here](https://cbea.ms/git-commit/)
+9. Make changes and push to your forked repository
+10. Create PR to the forked repository as mentioned below
+
+
 ### Pull Requests (PRs):
+<hr>
 
 1. **Fork the Repository**: Start by forking the repository to your GitHub account.