[Intermediate]: Prompt coderabbit on reviewing PR's

[aceppaluni]

🧩 Intermediate Friendly

This issue is a good fit for contributors who are already familiar with the Hiero C++ SDK and feel comfortable navigating the codebase.

Intermediate Issues often involve:

• Exploring existing implementations
• Understanding how different components work together
• Making thoughtful changes that follow established patterns

The goal is to support deeper problem-solving while keeping the task clear, focused, and enjoyable to work on.

Important

🧭 About Intermediate Issues

Intermediate Issues are a great next step for contributors who enjoy digging into the codebase and reasoning about how things work.

These issues often:

• Involve multiple related files or components
• Encourage investigation and understanding of existing behavior
• Leave room for thoughtful implementation choices
• Stay focused on a clearly defined goal

Other kinds of contributions — from beginner-friendly tasks to large system-level changes — are just as valuable and use different labels.

👾 Description of the Task

Currently, much of the review process is done by a maintainer. While this is good, we want to help maintainers speed up review time by implementing an AI tool Coderabbit.

💡 Proposed Approach

We propose to implement the coderabbit tool via config file and internal setup to assist maintainers and speed up review times.

👩‍💻 Implementation Steps

Implement a .coderabbit.yml workflow

Ensure the workflow contains the proper instructions needed to review PR's based on their skill and criteria.

✔️ Acceptance Criteria

• The task is completed as described
• All existing tests continue to pass
• No unrelated behavior or API changes are introduced
• Relevant documentation is updated if applicable

---

📋 Step-by-Step Contribution Guide

To help keep contributions consistent and easy to review, we recommend following these steps:

• Comment /assign to request the issue
• Wait for assignment
• Fork the repository and create a branch
• Set up the project using the instructions in README.md
• Make the requested changes
• Sign each commit using -s -S
• Push your branch and open a pull request

Read Workflow Guide for step-by-step workflow guidance.
Read README.md for setup instructions.

❗ Pull requests cannot be merged without S and s signed commits.
See the Signing Guide.

🤔 Additional Information

If you have questions while working on this issue, feel free to ask!

You can reach the community and maintainers here: Hiero-SDK-C++ Discord

Whether you need help finding the right file, understanding existing code, or confirming your approach — we're happy to help.

[rwalworth]

/finalize

[github-actions]

✅ Issue finalized by @rwalworth!

Skill level: Intermediate
Priority: priority: high

The issue body has been updated with the appropriate skill-level context and contribution guide. This issue is now ready for contributors to pick up via /assign.

[github-actions]

👋 Hey @aceppaluni! This issue has been inactive for 5 days.

Are you still working on this? We will close this in 2 days if we see no further activity.

If you're still on it, leave a comment to let us know! If you'd like to step down, comment /unassign.