Thank you for your interest in contributing! Coding Tentacle is a safety-first code repair agent, and we welcome contributions that improve its reliability, safety, or capabilities.
- Fork the repository on GitHub
- Clone your fork:
git clone https://github.com/YOUR_USERNAME/coding-tentacle.git - Install in development mode:
pip install -e ".[dev]" - Create a branch:
git checkout -b feature/your-feature-name
pip install -e ".[dev]"
pytest tests/ -v # Run test suite (must be 14/14)
ct version # Verify CLI works- Follow PEP 8 for Python code
- Use type hints where practical
- Keep functions small and focused β single responsibility
- Document public APIs with docstrings
- Never bypass the SecurityBrain VETO layer
- All generated code must pass through the safety scan pipeline
- If you add a new engine route, it must go through the same safety gates
- Test your changes against the security regression suite (10 tests)
- RED β GREEN β REFACTOR: Write a failing test first, then implement
- All 14 pytest tests must pass before submitting a PR
- Add tests for new functionality
- Regression suite (10 tests) must remain green
- Ensure tests pass:
pytest tests/ -v - Update documentation if you change behavior
- Keep PRs focused β one feature or fix per PR
- Write a clear PR description explaining what and why
- Reference any related issues
Write clear, concise commit messages:
type: Short description (max 72 chars)
Longer explanation if needed. What and why, not how.
Types: feat, fix, docs, test, refactor, chore, security
src/coding_tentacle/ # Main package
tests/ # Test suite (14 tests)
docs/ # Documentation
examples/ # Usage examples
research/ # Research notes and papers
scripts/ # Utility scripts
Open an issue or start a discussion. We're happy to help!
Thank you for making Coding Tentacle safer and better for everyone. π