chore(review): remove per-repo custom-codereview-guide skill - #249
Conversation
The skill was an OpenHands Option-1 overlay duplicating guidance that ships with the pr-review plugin's bundled /codereview skill (upstream @main). The generalized prompt stays upstream; repo-specific rules reach the reviewer via AGENTS.md. Tracking the upstream prompt upgrade in coldaine-codeOps#7.
🤖 CodeAnt AI — Review Status
|
Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
There was a problem hiding this comment.
Pull request overview
Removes the repository-local OpenHands “custom code review overlay” skill so cold reviews rely on the upstream /codereview guidance, with RobotOverview-specific constraints continuing to flow through AGENTS.md. This simplifies the workflow contract tests and CI path filtering by eliminating checks and triggers tied to the deleted skill file.
Changes:
- Deleted
.agents/skills/custom-codereview-guide.md. - Simplified
tools/ci/test_cold_review_workflow.pyto assert only the cold-review workflow path exists (and removed skill-content assertions). - Removed CI path filters in
.github/workflows/ci-tools-tests.ymlthat referenced the deleted skill file.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| tools/ci/test_cold_review_workflow.py | Drops the skill contract checks; keeps workflow-only contract assertions. |
| .github/workflows/ci-tools-tests.yml | Removes path triggers for the deleted skill file in PR/push filters. |
| .agents/skills/custom-codereview-guide.md | Deleted repository-specific review overlay skill. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
PR Summary by QodoRemove per-repo custom /codereview skill overlay and references
AI Description
Diagram
High-Level Assessment
Files changed (2)
|
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (3 files)
Documentation NoteThis PR correctly removes the per-repo Model/thinking level: step-3.7-flash (free tier), default reasoning — more limited than the production cold-review workflow's Stale Documentation (Out of Scope)
Reviewed by step-3.7-flash · Input: 59.2K · Output: 6.4K · Cached: 249.2K |
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTip of the day💡 Did you know, you can add REVIEW.md to your repo root and Qodo follows it on every PR |
Qodo FixerNo findings are available for this PR yet. Findings appear here once Qodo has reviewed the PR. |
User description
What
Removes
.agents/skills/custom-codereview-guide.md(the OpenHands-documented"Option 1: Custom Code Review Skill" per-repo overlay) and its references:
tools/ci/test_cold_review_workflow.py: drops theSKILLconstant and itsassertions;
test_workflow_and_skill_paths_exist→test_workflow_path_exists..github/workflows/ci-tools-tests.yml: removes the two path filters for thedeleted skill.
Why
The review-guidance content (commit hygiene, Renovate, severity format) already
ships with the
pr-reviewplugin's bundled/codereviewskill, pulled fromOpenHands/extensionsatmain— the generalized prompt lives where the botlives, not per-repo. RobotOverview-specific boundaries (Hangar vs BEAST-01,
Postgres-is-truth) still reach the reviewer through
AGENTS.md(the plugin'sdocumented "Option 2" channel). The reviewer is verified live: label, env,
secrets, App, runner group all present; runs execute on this repo today.
Tracked elsewhere
Workshopping/upgrading the upstream generalized prompt: coldaine-codeOps#7.
CodeAnt-AI Description
Remove the repository-specific code review overlay
What Changed
Impact
✅ One shared source for review guidance✅ Fewer obsolete review-guide checks✅ Cleaner CI path filtering💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.