docs: add compuse

[jdegand]

Summary by CodeRabbit

• Documentation
  • Added a new entry for the compuse library to the Angular resources list, describing a tool that analyzes Angular component usage and provides a unified API for extracting usage insights.
  • Updated the Official Resources section to include this reference without altering existing content or structure.

[coderabbitai]

Walkthrough

Added a single README.md entry for "compuse" including its GitHub link and a short description, placed under the Official Resources → Angular resources list.

Changes

Cohort / File(s)	Change Summary
README Documentation README.md	Added a new bullet: compuse with GitHub link and a brief description about analyzing Angular component usage across a codebase.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Single-line documentation addition with no code or behavioral impact
• Files to spot-check:
  • README.md — confirm formatting, link correctness, and placement under the intended section

Possibly related PRs

• docs: add AI resources and ng-openapi #1562 — Also adds a resource link to README.md; similar documentation-only change.
• docs: add ngx-gen-ui #1753 — Documentation-only PR that inserts a new resource entry in README.md.

Poem

🐰 I hopped into the docs today,
A tiny link in bold display,
Compuse now helps to find the trace,
Of components tucked in every place,
Hooray — another tool to play!

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'docs: add compuse' clearly and concisely describes the main change: adding a documentation entry for the compuse resource to the README.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 37ff960 and 70a97a8.

📒 Files selected for processing (1)

• README.md (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• README.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: 0

🧹 Nitpick comments (1)

README.md (1)

738-738: Optional: tighten the description for brevity.

Current copy is a bit wordy; consider a crisper utility‑focused phrasing.

-* [compuse](https://github.com/jakub-hajduk/compuse) - A library for analyzing Angular component usage, offering a unified interface to extract detailed usage insights.
+* [compuse](https://github.com/jakub-hajduk/compuse) - Analyze Angular component usage across your codebase with a unified API for extracting usage insights.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 49ab087 and 37ff960.

📒 Files selected for processing (1)

• README.md (1 hunks)

🔇 Additional comments (1)

README.md (1)

738-738: Entry looks good; confirm placement/link.

Formatting matches the list’s style. “Developer Tools” is a sensible category for a component‑usage analyzer. Please double‑check the GitHub link resolves and that there isn’t an existing duplicate entry elsewhere in the doc.