Thanks for your interest in contributing! This guide gets you from clone to PR in minutes.
git clone https://github.com/hibuka-labs/phi-agent.git
cd phi-agent
cargo build # pulls dependencies from crates.io automatically
cargo test # make sure everything passesThat's it. phi-agent uses pure crates.io dependencies — cargo build downloads everything you need. You don't need to clone any other repository for most contributions.
- Good First Issues — small, well-scoped tasks ideal for new contributors. Each one explains what to change and how to verify it.
- Help Wanted — larger features or improvements the maintainers would love help with.
- Got your own idea? Open an issue first to discuss it before writing code — saves you time if it doesn't fit the roadmap.
cargo fmt --check # Formatting
cargo clippy --all-targets -- -D warnings # Linting
cargo test # TestsAll three must pass. CI runs them automatically on every PR, so save yourself a round-trip.
- Create a feature branch from
master - Make your changes, with tests if applicable
- Run the checks above (
fmt,clippy,test) - Add an entry to
CHANGELOG.mdunder[Unreleased] - Open a PR with a clear description of what and why
We review PRs within 48 hours. Small, focused PRs (one logical change) get merged faster. If your PR is large, consider breaking it up.
- Present tense, imperative mood: "add feature" not "added feature"
- One logical change per commit
- Reference issues with
#123when applicable
If your change requires modifying a sibling crate (agent-base, agent-works, etc.) simultaneously:
# Clone the dependency alongside phi-agent
cd ..
git clone https://github.com/hibuka-labs/agent-base.git
cd phi-agent
# Temporarily add a path override in Cargo.toml (DO NOT COMMIT):
# agent-base = { version = "0.1.11", path = "../agent-base" }Remove the path override before committing. See CLAUDE.md for details on the multi-repo workflow.
Open a GitHub Discussion or an issue.