Skip to content

M4: Publish AI findings as GitHub PR checks and annotations #14

@dbrosio3

Description

@dbrosio3

Goal

Surface CI/PR AI findings through GitHub checks, summaries, annotations, and optional PR comments.

User value

Reviewers see AI feedback where they already work, with enough structure to decide whether to act.

Implementation notes

  • Publish a GitHub check summary from normalized review output.
  • Consider annotations for file/line findings.
  • Make PR comments optional to avoid noise.
  • Preserve artifacts for debugging provider behavior.

Risks / tradeoffs

  • PR comments can become noisy quickly.
  • GitHub Checks API behavior differs between Actions permissions and app-based integrations.

Suggested priority

P2

Milestone

M4: PR/CI AI review

TBD considerations

  • Preferred default surface: check summary only vs annotations vs comments.
  • Noise controls and deduplication strategy.

Acceptance criteria

  • AI findings appear in GitHub PR UI without requiring local hook output.
  • Commenting is configurable and defaults to low noise.
  • Output is generated from normalized review JSON.

Metadata

Metadata

Assignees

No one assigned

    Labels

    M4Milestone M4: PR/CI AI reviewP2Priority P2: later polishenhancementNew feature or requestv2ai-pushgate v2 roadmap

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions