diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644
index 0000000..647b788
--- /dev/null
+++ b/CONTRIBUTING.md
@@ -0,0 +1,65 @@
+# Contributing to Code-Contribution
+
+Thank you for your interest in contributing to Code-Contribution! We appreciate your efforts to improve the project. Please take a moment to review this guide to make the contribution process smooth and effective for everyone.
+
+## Table of Contents
+1. [Getting Started](#getting-started)
+2. [Reporting Bugs](#reporting-bugs)
+3. [Suggesting Enhancements](#suggesting-enhancements)
+4. [Contributing Code](#contributing-code)
+5. [Coding Guidelines](#coding-guidelines)
+6. [Code Review Process](#code-review-process)
+7. [License](#license)
+
+## Getting Started
+
+1. **Fork the repository** to your own GitHub account.
+2. **Clone your forked repository** to your local machine:
+
+   ```bash
+   git clone https://github.com/your-username/Code-Contribution.git
+4. **Install dependencies** if any are specified in the README.md.
+5. Create a new branch for each feature or bug fix:
+   
+   ```bash
+    git checkout -b feature/your-feature-name
+## Reporting Bugs
+If you find a bug, please open an issue. Include details such as:
+
+- A clear and descriptive title
+- Steps to reproduce the issue
+- Expected behavior and actual behavior
+- Screenshots, if applicable
+- Environment (OS, language version, etc.)
+
+## Suggesting Enhancements
+Enhancement suggestions can be submitted as issues. Include:
+
+- A descriptive title
+- The motivation and benefits of the enhancement
+- Relevant examples, links, or code snippets
+## Contributing Code
+1. Ensure your code is well-documented and adheres to the Coding Guidelines.
+2. Write clear commit messages.
+3. Add test cases for any new functionality, if applicable.
+4. Push your branch to GitHub:
+5. 
+   ```bash
+   git push origin feature/your-feature-name
+
+6. Open a Pull Request (PR) to the main branch of Code-Contribution with:
+- A descriptive title and summary
+- A link to any related issues
+- A list of changes made
+## Coding Guidelines
+- **Code Style:** Follow consistent and readable code conventions.
+- **Documentation:** Document your code where necessary.
+- **Tests:** Run existing tests and add tests for new features.
+## Code Review Process
+1. Pull requests will be reviewed by the maintainers. Be prepared to make revisions based on feedback.
+2. Once approved, your code will be merged into the main branch.
+3. If your contribution adds substantial changes, ensure that they are well-tested and documented.
+## License
+By contributing, you agree that your contributions will be licensed under the same license as Code-Contribution.
+
+### Thank you for helping improve Code-Contribution!