chore: consolidate homebrew tap to panbanda/brews

[panbanda]

Summary

• Update release workflow to publish formula to panbanda/homebrew-brews instead of panbanda/homebrew-omen
• Update README install instructions to use brew install panbanda/brews/omen

Summary by CodeRabbit

• Chores
  • Updated Homebrew installation tap location and corresponding installation instructions in documentation.

[github-actions]

Omen Analysis

Diff Risk

Risk Score	22%
Risk Level	LOW
Files Modified	2
Lines Added	+2
Lines Deleted	-2
Commits	2

Risk Factors

Factor	Score
file_churn	0.1
entropy	0.0466
commits	0.0140
num_files	0.0106
lines_added	0.0008
lines_deleted	0.0008
file_complexity	0
ownership_diffusion	0

Recommendations

• Touches historically volatile files - changes here often introduce bugs

Repository Health

Health Score	77.24425991880834 / 100
Grade	C
Files Analyzed	101
Critical Issues	1

Score Components

Component	Score	Weight
complexity	92	1
duplication	42	0.8
cohesion	94.2	0.6
tdg	81.9	0.6
coupling	53.1	0.4
satd	91.1	0.4
smells	100	0.2

Tips for AI agents

Use these commands to investigate and improve low-scoring areas.

Run full analysis:

omen -f json score    # health score with component breakdown
omen -f json diff     # PR risk analysis
omen hotspot          # high-churn + high-complexity files

Coupling (score: 53.110891089108904) -- needs attention

omen graph && omen smells

Break cyclic dependencies by introducing interfaces or extracting shared types. Reduce fan-out from hub modules by splitting responsibilities.

---

Duplication (score: 42.047601744186046) -- needs attention

omen clones

Look for Type-1 (exact) and Type-2 (renamed) clones. Extract shared logic into reusable functions or modules. Prioritize clones in high-churn files.

---

General workflow for improving scores:

1. Run the relevant analyzer command to identify specific files
2. Focus on the highest-weight components first (complexity 25%, duplication 20%, cohesion 15%, TDG 15%)
3. Make targeted improvements -- small refactors that reduce complexity or eliminate duplication
4. Re-run omen score to verify improvement

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 23b0db1 and fb6ceef.

📒 Files selected for processing (2)

• .github/workflows/release.yml
• README.md

---

📝 Walkthrough

Walkthrough

Homebrew tap repository reference updated from panbanda/homebrew-omen to panbanda/homebrew-brews in GitHub Actions workflow and README, maintaining existing functionality.

Changes

Cohort / File(s)	Summary
Build Configuration .github/workflows/release.yml	Updated Homebrew tap repository URL in formula generation step.
Documentation README.md	Updated Homebrew installation tap reference in installation instructions.

Suggested labels

risk: low

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	Title accurately summarizes the main change: consolidating the Homebrew tap from panbanda/homebrew-omen to panbanda/homebrew-brews.
Pr Test Coverage & Quality Check	✅ Passed	PR contains only configuration and documentation changes (release.yml, README.md). No code, functions, methods, classes, endpoints, or journeys modified.

_{✏️ 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/consolidate-homebrew-tap

---

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.}