# Contributing to aam-cli
Thanks for your interest in contributing.
## Before You Start
- Search existing issues and pull requests first.
- Open an issue before implementing large changes.
- Keep pull requests focused and small.
## Development Setup
```bash
cargo build
cargo test
```
## Coding Guidelines
- Follow the standard Rust style and run formatting tools before submitting.
- Prefer clear naming and small functions.
- Add or update tests for behavior changes.
- Update docs when command behavior or flags change.
## Commit and PR Guidelines
- Use descriptive commit messages.
- Link related issue numbers in PR descriptions.
- Include motivation, implementation notes, and validation steps.
- Mention possible breaking changes explicitly.
## Pull Request Checklist
- [ ] Builds successfully.
- [ ] Tests pass locally.
- [ ] New or changed behavior is covered by tests.
- [ ] Documentation is updated where needed.
- [ ] PR description explains why and how.