Skip to content

Generalize pr-review into a context-adaptive review agent (artifact contract + rubric registry) #610

Closed
6 of 6 issues completed

Description

@github-actions

Refactor the existing pr-review agent into a single context-adaptive review agent that selects its rubric and output channel from an explicit artifact contract {artifact_type, content_ref, rubric, output_channel} instead of being hard-wired to pull requests. One maintained review brain, taught new artifact types over time.

Sequencing (from discussion #607's Suggested Next Step):

  1. Behavior-preserving extraction: introduce the contract + a rubric registry with pr_diff as the sole registered type, mapping to today's prompts/ cascade and inline-review output channel. Prove the existing PR-review suite passes unchanged.
  2. Register plan_json (the fixed plan-critic rubric + structured-findings channel) to satisfy Epic Initiative: Adversarial plan-critic + structural gates for the initiative-planner (Bob) #597's [Phase 2] Adversarial plan-critic pass against the fixed rubric #603, re-scoped to "invoke the review agent with the plan rubric."
  3. Register skill_candidate (Epic Initiative: Eval-gated, human-reviewed self-improving skills (SkillOpt-style) #581's eval criteria + pass/score channel).
  4. Coordinate with the Safe Release Strategy (Epic Initiative: Safe Release Strategy for Agentic Workflows (versioning · rings · canary) #495) so any change to pr-review rides ring/channel promotion rather than shipping straight to stable.

Not a duplicate of #597 or #581 — this is the shared review brain those initiatives consume. The hard constraint throughout: pr_diff is behavior-preserving and well-tested before any new artifact type lands. Source: discussion #607.


Planned from idea discussion #607 by the BMAD Scrum Master initiative-planner. Inert until a maintainer adds initiative:auto.

Activity

  1. added
    initiative:autoDriver may auto-release this epic's ready sub-issues to dev-lead
    on Jun 12, 2026
  2. don-petry commented on Jun 14, 2026

    @don-petry
    Collaborator

    Update (2026-06-14):

    Per this epic's sequencing, next up: register plan_json (the fixed plan-critic rubric + structured-findings channel, which satisfies epic #597's #603), then skill_candidate (epic #581's eval criteria), coordinated with the Safe Release Strategy (#495). Epic stays open.


    Generated by Claude Code

  3. don-petry commented on Aug 20, 2026

    @don-petry
    Collaborator

    Initiative driver — stale in-flight slot(s) detected

    The following open sub-issue(s) still carry the dev-lead label but have
    had no dev-lead activity for ≥ 72h, so they are occupying an in-flight
    slot without progressing: #616.

    No labels were changed. A human should decide whether to split-and-close, retry,
    or park each one so the slot is freed for the rest of the epic.

  4. don-petry commented on Oct 21, 2026

    @don-petry
    Collaborator

    Closing after the 2026-10-21 backlog triage.

    Why: All registry stories closed; last story #616 effectively done (stable includes refactor).
    Evidence: subs 611-615 closed; PR #622

    Reopen if this still reproduces on main.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    initiativeEpic / initiative tracking issueinitiative:autoDriver may auto-release this epic's ready sub-issues to dev-lead

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions