Add PgQue to tools.yaml

[gmcabrita]

Add PgQue as durable event stream replacement (Kafka, Redpanda, etc).

Summary by CodeRabbit

• New Features
  • Added a new software tool entry for PgQue, including its description, problem statement, category, repository link, and replacement details.

[coderabbitai]

Warning

Review limit reached

@gmcabrita, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 58 minutes and 47 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 8cbc122c-0ef6-4bae-bcf6-407de7efa9de

📥 Commits

Reviewing files that changed from the base of the PR and between adb24c9 and 944d10b.

📒 Files selected for processing (1)

• src/content/tools.yaml

📝 Walkthrough

Walkthrough

A new PgQue tool entry was added to the Message Queues & Background Jobs catalog section in src/content/tools.yaml, including its metadata, repository URL, replacement targets, and tool type.

Changes

Message queues catalog update

Layer / File(s)	Summary
Add PgQue tool entry src/content/tools.yaml	Adds a new pgque YAML item for PgQue with its description, problem statement, category, repository URL, replaces list, and toolType.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A bunny hopped by, ears in the breeze,
Found PgQue nestled in the YAML trees.
One little entry, neat and new,
With queue-time hops and Postgres glue.
🐇✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and concisely describes the main change: adding PgQue to tools.yaml.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[qodo-code-review]

PR Summary by Qodo

Add PgQue to tools catalog (tools.yaml)
📝 Documentation 🕐 Less than 5 minutes

Description

• Add PgQue as a queue/event-stream tool entry in the catalog.
• Position PgQue as a durable event stream alternative to Kafka/Redpanda.
• Link to upstream repository and classify under queues.

High-Level Assessment

Current approach (adding a new tools.yaml entry) is the right fit for expanding the catalog. Only verification needed is content accuracy (description text/typos) and that the chosen category/replaces fields match existing taxonomy conventions.

Files changed (1) +9 / -0

Documentation (1) +9 / -0

tools.yamlAdd PgQue tool entry under queues +9/-0

Add PgQue tool entry under queues

• Introduces a new tools catalog entry for PgQue including description, problem statement, URL, category, and replacement positioning (Kafka/Redpanda). Keeps the existing structure and metadata fields consistent with neighboring entries.

src/content/tools.yaml

[Copilot]

Pull request overview

Adds PgQue to the project’s tools.yaml catalog as a Postgres-based queue/event-stream option, positioned as an alternative to heavier durable streaming systems.

Changes:

• Added a new pgque tool entry under Message Queues & Background Jobs.
• Tagged it as replacing Kafka/Redpanda and linked to the project repository.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0) 🎨 UX issues (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

1. Description typo ✓ Resolved 🐞 Bug ⚙ Maintainability

Description

The new PgQue entry’s description contains a duplicated word (“on top of on”), which will be
displayed verbatim in the UI and included in the searchable text.

Code

src/content/tools.yaml[74]

+  description: Zero-bloat Postgres queue built on top of on battle-proven Skype's PgQ

Evidence

The typo is present in the newly-added YAML entry, and the UI renders description directly and
includes it in the data-searchable string, so the typo will surface on the site and in search
text.

src/content/tools.yaml[72-79]
src/components/ToolCard.astro[20-46]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The `pgque` tool entry description has a typo: `built on top of on ...` (duplicated `on`). This text is displayed directly in the tool card and is also used in the `data-searchable` attribute.

### Issue Context
Tool descriptions are user-facing and used for search; typos degrade perceived quality and search relevance.

### Fix Focus Areas
- src/content/tools.yaml[72-75]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@src/content/tools.yaml`:
- Line 74: The description text for the PgQue entry contains a duplicated phrase
(“top of on”) that should be cleaned up. Update the description in the tools
metadata so it reads naturally and correctly, using the existing
PgQue/description field to locate the text, and remove the extra “on” while
preserving the intended meaning.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 4f14dffd-372c-4eaa-95cb-bf66fd3d8b06

📥 Commits

Reviewing files that changed from the base of the PR and between dd76c88 and adb24c9.

📒 Files selected for processing (1)

• src/content/tools.yaml