Repository navigation
Contributing
Yogeswaran Amsavalli edited this page Oct 3, 2026
·
1 revision
Thanks for helping. Keep changes small and focused.
- Open an issue first for anything bigger than a small fix, so you know it's wanted before you build it.
-
Fork the repo and branch from
main:-
feature/<what>for something new -
fix/<what>for a bug -
docs/<what>for documentation
-
- Keep pull requests small. One change per PR is easier to review.
-
Run the checks. Build Debug and Release and run every
checks/*.cs. See Building and Checks. -
Open the PR against
main. It needs one approval and is squash-merged.
Match the code around you: its naming, its comment density, and comments that say why in plain sentences. Logic that can live without WPF does (like IslandTrigger), with cases in checks/.
Clayo reads ~/.claude/projects and never writes there. Keep it that way: Clayo's own files go in %LOCALAPPDATA%\Clayo.
Don't open a public issue. Report it privately from the repo's Security tab (Report a vulnerability).
Clayo is MIT licensed. By contributing you agree your contribution is under the same license.
Clayo · MIT · Not affiliated with Anthropic
Using Clayo
Under the hood