[compound-engineering] Bug: ce:compound routes generic code-heavy issues to kieran-rails-reviewer

[ChushulSuri]

Bug Description

Component: Skill - ce:compound
Summary: ce:compound appears to route any code-heavy issue to kieran-rails-reviewer, even though that reviewer is explicitly Rails-specific.

Environment

• Plugin Version: 2.28.0
• Agent Platform: OpenCode
• Agent Version: 1.3.13
• OS: Darwin 25.3.0 x86_64

What Happened

While reviewing the CE skills and agents for use in a non-Rails repo, I found that ce:compound contains this routing rule:

• Any code-heavy issue -> kieran-rails-reviewer + code-simplicity-reviewer

At the same time, the kieran-rails-reviewer agent description is clearly Rails-only:

• selected when the diff touches Rails application code
• focused on Rails conventions, Turbo/Hotwire, service objects, and Rails maintainability concerns

This means ce:compound can route generic code-heavy issues to a Rails-specific reviewer even in non-Rails repositories.

Expected Behavior

ce:compound should use stack-aware reviewer selection.

For non-Rails repos, generic code-heavy issues should not be routed to kieran-rails-reviewer. The workflow should preserve strong code review coverage without assuming Rails.

Steps to Reproduce

1. Inspect the routing instructions in ce:compound.
2. Note the rule:
   • Any code-heavy issue -> kieran-rails-reviewer + code-simplicity-reviewer
3. Inspect kieran-rails-reviewer.
4. Note that the reviewer is explicitly Rails-specific.
5. Apply ce:compound in a non-Rails repo and observe that the reviewer selection logic is overly Rails-biased for generic code-heavy issues.

Error Messages

No runtime error message. This appears to be a reviewer-selection / workflow design bug.

---

Reported via /report-bug-ce skill

[tmchow]

Will dig in.