Skip to content

Agent fix-handoff blocks + follow-up-issue suggestions #1962

Description

@JSONbored

Phase 2 — Interactive control & issue intelligence

Context

We surface findings but don't help apply them. The contributor boundary forbids server-side writes to contributor code; the local-write-action-spec pattern (src/mcp/local-write-tools.ts) already lets the contributor's own agent execute actions.

Goal

Emit a machine-readable fix-handoff block per finding, and offer to file a follow-up issue for deferred findings.

Requirements

  • Per finding, attach a structured "apply this fix" prompt block that the contributor's own local coding agent can consume — content only; execution stays on the contributor's machine (boundary-safe).
  • A "file a follow-up issue" action via the existing gittensory_file_issue local-write spec for findings a maintainer wants tracked rather than blocked.
  • Default-OFF; public-safe; no cloud/server write to contributor code.

Deliverables

  • Handoff-block renderer + follow-up-issue action + tests + docs.

Expected outcome

  • Findings become actionable without breaking the contributor boundary; less manual copy-paste.

Effort

M.

Metadata

Metadata

Assignees

No one assigned

    Labels

    gittensor:featureGittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.orbGittensory Orb related - maintainer self-hosting analytics.

    Projects

    Status
    Done

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions