Thanks for contributing to this project.
- Read README.md for the project overview.
- Use QUICKSTART.md for the local setup path.
- Check existing issues and pull requests before opening new work.
git clone https://github.com/KazKozDev/dspy-optimization-patterns.git
cd dspy-optimization-patterns
poetry install --with dev
cp .env.example .envSet OPENAI_API_KEY before running optimization or API flows that require model access.
- Create a branch for your change.
- Keep changes scoped to one problem or feature.
- Update docs, examples, or tests when behavior changes.
- Run local checks before opening a pull request.
make lint
make testUseful commands:
make prepare-sample-data
make optimize-rag
make run-apiPlease make sure your pull request:
- explains the problem and the chosen solution
- stays focused and avoids unrelated cleanup
- includes test coverage or explains why tests were not added
- updates README or other docs if the public workflow changed
Small, reviewable pull requests are preferred over large multi-purpose changes.
When opening an issue, include:
- what you expected
- what happened instead
- steps to reproduce
- relevant logs, stack traces, or screenshots
- environment details if the bug is setup-dependent
- Follow the existing Python and project structure.
- Keep documentation concise and operational.
- Avoid introducing new tooling unless it solves a clear project need.