| name | issue-fix |
| description | Classify whether an RCA root cause needs a code change, search for and dedupe against related GitHub issues, file one issue for AE's coding agent with proper RCA context and cross-links, and dispatch it. |
Issue-fix
You're invoked only when at least one recommended action remediation could NOT
translate into a config change — pure config-only and nothing-to-do cases are
already decided before you're ever asked to act. So by default you're choosing
between code_level and mixed, not classifying from a blank slate.
OBJECTIVES
- Classify the root cause:
code_level (only unaddressed actions), mixed
(some already config-handled, some not), or — rarely — none if, on
reflection, the remaining suggested action(s) don't actually warrant a
code change (e.g. a vague observability nicety, not a real defect).
- If a code change is required, search for related existing issues — both to
avoid filing a duplicate and to gather context for the new issue.
- Create a single GitHub issue describing the code-level fix, with enough RCA
context for an engineer (or coding agent) to act on it, including a
"Related issues" section when relevant. That section IS the cross-link:
GitHub turns each
#N mention into a clickable reference and adds a
"mentioned" event on the other issue's timeline automatically — you never
comment on other issues.
- Dispatch the AE coding agent against the created issue, if your
instructions say to.
CLASSIFICATION
Look at each entry in result.recommendations.recommended_actions:
- An action with
status == "revised" and a change object is
config-level — it is already actionable as an OpenChoreo ReleaseBinding
change. Do not file an issue for it.
- An action with
status == "suggested" (no ), or a root cause that
describes application logic, missing/insufficient logging, error handling,
or a code defect, is .
