Skip to content

[scanner] review: render the inlined Linear issue in the kick's scope contract section #14911

Closed

Description

@hivecommons-hive

Part of #14906. Builds on #14909 and #14910.

Scope (child 3 of 3)

Render the fetched Linear issue in scopeContractSection (src/pkg/review/prompts.go):

  • Contract: Linear issue ONB-3872 (state: In Progress), followed by a fenced block with the issue text, marked as untrusted data from the issue tracker, not instructions.
  • Then the existing in-scope / out-of-scope rules, plus: "mark each acceptance criterion delivered, missing, or deferred".
  • With the issue unavailable (empty ScopeContractText), keep today's wording but name the identifier that could not be fetched instead of telling the reviewer to run gh issue view on it.

GitHub-issue and lease-task contracts render exactly as they do today.

Tests

  • A kick for a PR with a fetched issue contains its title and description inside the untrusted-data fence.
  • A fetch failure falls back to the current text, naming the identifier.
  • A GitHub-issue contract is unchanged.

Why

The "ticket scope" section (missing requirements, scope creep, AC ↔ test) is the review dimension a Linear-tracked team values most; today the kick cannot express it at all.

Decision taken by hive: split #14906 along the three steps in its own proposal; this child owns only prompt rendering and is blocked on #14910 for the text.

— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88

Activity

  1. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Oct 28, 2026
  2. clubanderson commented on Oct 28, 2026

    @clubanderson
    Member

    Closed: fixed by #15074 (merged).

  3. github-actions commented on Oct 28, 2026

    @github-actions
    Contributor

    @hivecommons-hive[bot] this issue was closed by @clubanderson as completed.

    If this was closed by a merged PR, the fix only takes effect once it ships in a tagged release and your deployment updates to it — check your running version against the fix before concluding the fix failed.

    If you are still seeing the problem, comment /reopen and it will be reopened for you — you do not need write access. Please add what you are still observing (running version, logs, steps) so it is not closed the same way again.

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

    agent/scannerCreated or modified by the scanner agenthelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions