feature: Add action to run pr-agent

[rosariosm]

What's this PR do?

Summary of changes in this PR or what it accomplishes.

@ulises-jeremias

Summary by CodeRabbit

• Chores
  • Added automated workflow for pull request analysis and review processes.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

A new GitHub Actions workflow is introduced that automates pull request reviews using the pr-agent action. The workflow triggers on PR lifecycle events and comments, runs with necessary repository permissions, and passes required credentials as environment variables.

Changes

Cohort / File(s)	Change Summary
GitHub Actions workflow \.github/workflows/pr_agent\.yml	Added new workflow file that configures automated PR review automation with event triggers (pull_request, issue_comment) and action execution with token/key environment variables

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Straightforward configuration addition with standard GitHub Actions syntax
• Single new file with no conditional logic or complex branching
• No changes to existing code or dependencies

Poem

🐰 A workflow springs to life with a hop,
pr-agent guards every PR without stop,
With tokens and keys all safely in place,
Reviews bloom with automated grace! 🌳✨

✨ 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 1ebabd0 and 1c8fabd.

📒 Files selected for processing (1)

• .github/workflows/pr_agent.yml (1 hunks)

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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