Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Review queue: let reviewers add context before approving

Offen
  • Stimmt etwas nicht?
#364 1 Kommentar 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@NathanTarbert arbeitet bereits daran.

Seit 12.10.2026.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

enhancement

Summary

Let a reviewer add free-text context to a review-queue item before approving it, so the published article reflects knowledge the assistant did not have. Follow-up to the review queue in #362.

Problem

Many unseen questions arrive with no usable draft, because the assistant had nothing to ground an answer on. Those items are flagged "No usable answer" and the reviewer has to write the whole answer from scratch in a single textarea. The same reviewer often has useful raw material (a product detail, a link, a policy snippet, an internal explanation) that would be easier to paste than to turn into a finished answer. A Reddit commenter also asked for a way to give the system "direct inputs of additional information" that improve answer quality.

Proposed behavior

  • On each pending item in the Review tab, add an Additional context field next to the question and answer.
  • The context is free text (suggest a max of 8,000 characters, matching the answer limit).
  • On approve, the published article is built from the reviewer's final question and answer; the context is used to help produce that answer (see open question) and is stored with the item for audit.
  • Context is private to the workspace and never served directly. Only the approved article is.

Open questions to settle before building

  1. Does the context get turned into an answer automatically, or is it just a scratchpad? Options: (a) reviewer-only notes that stay on the item, (b) an optional "Draft answer from context" button that asks the model to write an answer from the context, which the reviewer then edits and approves, (c) append the context to the article body. Recommendation: (b), because it keeps a person in the loop and fills the empty-draft case.
  2. Should a context-only entry exist without a captured question? A standalone "add knowledge" form (question + answer + context, no queue item) is a separate, simpler path that reuses the same article creation. Recommendation: include it in this issue as a second entry point, since it is the same code path and directly serves the "add extra context to the KB" ask.
  3. Cost and rate limits. Drafting from context calls the model, so it needs the same per-org rate limiting and plan quota treatment as other generation paths.

Implementation notes

  • UI: app/(dashboard)/kb/review-tab.tsx.
  • API: extend PATCH /api/kb/review/[id] (new optional field, or a separate action for drafting), plus a new route if the standalone form is included. Keep owner/admin-only and Pro-gated.
  • Data: add a nullable context column to kb_review_items via a new idempotent migration.
  • Reuse embedText, the 2000-article cap in lib/kb/limits.ts, and rateLimitShared.
  • Docs: update the Review queue section in content/docs/product/knowledge-base.mdx and reference/data-model.mdx.

Acceptance criteria

  • A reviewer can add context to a pending item and save it without approving
  • An item with no draft can be answered from context without retyping everything
  • Approving still requires a non-empty reviewed answer
  • Context is never searchable or served until it is part of an approved article
  • Owner/admin only, Pro-gated, rate limited, org-scoped
  • Docs, unit, component and e2e tests updated
Vorherrschende Sprache
TypeScript
Sterne
16
Forks
2
Ø Merge
7 Std. 22 Min.
Gemergte PRs (30 T.)
150

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus answerLoops/answerLoops

Alle Issues in answerLoops/answerLoops

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.