fix: Add a CHANGELOG.md (#64)

path/to/CHANGELOG.md

@@ -0,0 +1,14 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+- Initial release.
+
+## [v0.1.0] - 2023-10-01
+
+- Initial release with basic functionality.

path/to/CONTRIBUTING.md

@@ -0,0 +1,21 @@
+# Contributing
+
+We welcome contributions from the community! Please follow these guidelines when submitting changes.
+
+## Updating the Changelog
+
+All changes must be reflected in the [CHANGELOG.md](CHANGELOG.md). When you make a significant change:
+
+1. Ensure it aligns with our [Semantic Versioning](https://semver.org/spec/v2.0.0.html) policy.
+2. Add an entry under the appropriate version section in the Changelog.
+3. Include a brief description of the change and any notable impacts.
+
+Keep the Changelog format consistent with the [Keep a Changelog](https://keepachangelog.com/en/1.0.0/) guidelines.
+
+## Pull Requests
+
+- Make sure your feature branches are up-to-date with the main branch.
+- Include tests for new functionality.
+- Describe the motivation and changes in the PR description.
+
+We'll review your PR and provide feedback.