Thanks for your interest in contributing. This guide covers how to report issues, suggest features, and submit code.
Open a GitHub Issue with:
- A clear, descriptive title
- Steps to reproduce the bug
- Expected vs. actual behavior
- Environment details (Node version, OS, SDK version)
- Relevant logs or error messages
Check existing issues first to avoid duplicates.
Open a GitHub Issue or start a Discussion with:
- The problem you're trying to solve
- Your proposed solution
- Any alternatives you've considered
git clone https://github.com/van-reflect/Reflect-Memory.git
cd Reflect-Memory
npm installCreate a .env file in the project root:
REFLECT_API_KEY=your_api_key_here
Get an API key at reflectmemory.com.
- TypeScript is the primary language. All new code should be written in TypeScript.
- Use strict typing, avoid
anywhere possible. - Do not add comments that merely narrate what the code does. Comments should explain why, not what.
- No AI-generated comments, no boilerplate comment blocks.
- Use
constoverletwhen the variable is not reassigned. - Keep functions small and focused.
- Fork the repo and create a branch from
main. - Make your changes in a focused, single-purpose branch.
- Write or update tests if applicable.
- Make sure the build passes and there are no lint errors.
- Open a PR against
mainwith:- A clear title describing the change
- A summary of what changed and why
- Links to any related issues
- A maintainer will review your PR. Be responsive to feedback.
- Keep PRs small. Smaller PRs get reviewed faster.
- One logical change per PR.
- Rebase on
mainbefore opening if your branch is behind.
This project follows the Contributor Covenant Code of Conduct. By participating, you agree to uphold a respectful, inclusive environment.
By contributing, you agree that your contributions will be licensed under the MIT License.