Contributing

Thanks for contributing to coding-agent-sync.

Before opening a PR

Open an issue first for substantial changes (new commands, behavior changes, or release/process changes).
Keep changes focused and avoid unrelated refactors.
Add/update tests for behavior changes.
Run local validation:

go test ./...
go build ./...
go vet ./...

Use a Conventional Commit style PR title, for example:
- feat: add linux release artifact
- fix: handle missing global instructions path
- docs: clarify install instructions
Update docs (README.md, docs/release.md) when user-facing behavior changes.
Keep CI green.

Releases are managed by release-please from main. See docs/release.md for details.