ci(claude): link to CONTRIBUTING.md and add format step

Reference CONTRIBUTING.md from commit and PR skills so conventions
stay in sync. Add make format / astyle step to commit skill.
This commit is contained in:
Jacob Dahl 2026-03-17 19:22:16 -08:00 committed by Ramon Roche
parent 2ea2bfcc15
commit 8aa02078e9
2 changed files with 6 additions and 1 deletions

View File

@ -12,6 +12,8 @@ Create a git commit: `type(scope): description`
**NEVER add Co-Authored-By lines. No Claude attribution in commits.** **NEVER add Co-Authored-By lines. No Claude attribution in commits.**
Follow [CONTRIBUTING.md](../../CONTRIBUTING.md) for full project conventions.
## Steps ## Steps
1. Check branch (`git branch --show-current`). If on `main`, create a feature branch. Use `<username>/<description>` format where `<username>` comes from `gh api user --jq .login`. If unavailable, just use `<description>`. 1. Check branch (`git branch --show-current`). If on `main`, create a feature branch. Use `<username>/<description>` format where `<username>` comes from `gh api user --jq .login`. If unavailable, just use `<description>`.
@ -21,7 +23,8 @@ Create a git commit: `type(scope): description`
5. Write concise imperative description, lowercase, no period, under 72 chars. 5. Write concise imperative description, lowercase, no period, under 72 chars.
6. Breaking changes: `type(scope)!: description` 6. Breaking changes: `type(scope)!: description`
7. Body (if needed): explain **why**, not what. 7. Body (if needed): explain **why**, not what.
8. Stage and commit. No `Co-Authored-By`. 8. Run `make format` or `./Tools/astyle/fix_code_style.sh <file>` on changed C/C++ files before committing.
9. Stage and commit. No `Co-Authored-By`.
## Examples ## Examples

View File

@ -10,6 +10,8 @@ allowed-tools: Bash, Read, Glob, Grep
**No Claude attribution anywhere (no Co-Authored-By, no "Generated with Claude").** **No Claude attribution anywhere (no Co-Authored-By, no "Generated with Claude").**
Follow [CONTRIBUTING.md](../../CONTRIBUTING.md) for full project conventions.
## Steps ## Steps
1. Check branch. If on `main`, create a feature branch. Use `<username>/<description>` format where `<username>` comes from `gh api user --jq .login`. If unavailable, just use `<description>`. 1. Check branch. If on `main`, create a feature branch. Use `<username>/<description>` format where `<username>` comes from `gh api user --jq .login`. If unavailable, just use `<description>`.