feat: add branch naming conventions in CLAUDE.md

[sylr]

No description provided.

[coderabbitai]

Walkthrough

Added a "Ledger" section to project documentation that defines standardized branch naming conventions. Includes enumerated prefixes (feat/, fix/, refactor/, test/, docs/, chore/, style/, perf/, build/, release/, hotfix/) with their intended usage and release branch patterns.

Changes

Cohort / File(s)	Summary
Documentation CLAUDE.md	Added "Branch naming convention" subsection under new "Ledger" section, documenting standardized branch prefixes and their purposes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 Branches now have names so clear,
Feat, fix, and docs without fear!
A naming path, so neat and bright,
Our warren's workflow feels just right! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	No pull request description was provided by the author, making it impossible to assess whether the description relates to the changeset.	Add a pull request description explaining the purpose of the branch naming conventions and why they were added to CLAUDE.md.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'feat: add branch naming conventions in CLAUDE.md' accurately describes the main change—adding documentation about branch naming conventions to the CLAUDE.md file.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/add-claude-md

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@CLAUDE.md`:
- Around line 14-15: Standardize the branch-pattern examples so both use the
same trailing-slash style: change either `release/<version>` to
`release/<version>/` or `hotfix/<version>/` to `hotfix/<version>` in CLAUDE.md
so both patterns match consistently (e.g., make both `release/<version>` and
`hotfix/<version>`).

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 218ef795-9b44-4abb-a93e-f63ce352dde1

📥 Commits

Reviewing files that changed from the base of the PR and between 1e1d21c and b1202fb.

📒 Files selected for processing (1)

• CLAUDE.md

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.31%. Comparing base (1e1d21c) to head (b1202fb).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1288      +/-   ##
==========================================
- Coverage   79.42%   79.31%   -0.11%     
==========================================
  Files         205      205              
  Lines       10998    10998              
==========================================
- Hits         8735     8723      -12     
- Misses       1567     1577      +10     
- Partials      696      698       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.