# Contributing
Thanks for helping improve PrismTTY.
## Development Setup
Install Rust, PCRE2, and `pkg-config`, then run:
```sh
cargo fmt --check
cargo test
cargo clippy --all-targets -- -D warnings
```
Generated shell completions must stay in sync with the CLI:
```sh
cargo run --features completion-generation --bin gen-completions
git diff --exit-code completions/
```
## Fixtures and Test Data
Use synthetic fixtures only. Do not commit real terminal captures, private
device output, customer names, credentials, personal filesystem paths, or trace
files from administrative sessions.
When adding replay fixtures, use invented hostnames, documentation-range IP
addresses, and the minimum command output needed to exercise the rule or parser
behavior under test.
## Pull Request Checklist
- Run `cargo fmt --check`.
- Run `cargo test`.
- Run `cargo clippy --all-targets -- -D warnings`.
- Regenerate completions when CLI flags or command help changes.
- Update `README.md` or `CHANGELOG.md` when user-facing behavior changes.
- Keep release, Homebrew, and workflow changes reproducible from checked-in
scripts.
## Security-Sensitive Changes
Be careful around these boundaries:
- Remote terminal output processed by the highlighter.
- YAML config and profile parsing.
- PTY command execution and argument handling.
- Runtime reload marker files.
- Trace output generated by `--trace-io`.
- GitHub Actions release publication and package checksums.
Prefer small, reviewable changes with regression tests for these areas.