Skip to content

fix(ci): plain triage reply tone, no Cursor disclaimer#2447

Merged
binaricat merged 1 commit into
mainfrom
fix/cursor-triage-reply-tone
Jul 24, 2026
Merged

fix(ci): plain triage reply tone, no Cursor disclaimer#2447
binaricat merged 1 commit into
mainfrom
fix/cursor-triage-reply-tone

Conversation

@binaricat

Copy link
Copy Markdown
Owner

Summary

  • Remove public This was generated by Cursor automation. from issue/PR comments (internal HTML marker kept).
  • Require code paths/symbols only in code_findings / reasoning; public reply is plain maintainer language.
  • Classify prompt: short sentences, UI labels, no symbol dumps or heavy () / 「」.
  • Soften automatic rewrite templates the same way.

Test plan

  • node --test scripts/cursor-automation.test.cjs (66 pass)
  • Next classify on a new issue should read natural and omit the disclaimer

Public issue comments no longer show a generated-by line. Grounding stays
in code_findings/reasoning only so reply can use UI language without file
paths, symbols, or dense parentheses. Classify prompt and rewrite templates
match that tone.
@binaricat
binaricat merged commit 3ff1692 into main Jul 24, 2026
6 of 7 checks passed
@binaricat
binaricat deleted the fix/cursor-triage-reply-tone branch July 24, 2026 07:08
@github-actions github-actions Bot added the automation:codex-loop Own/bot PR waiting on Codex review↔fix loop label Jul 24, 2026

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 089f2bcfb0

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

const blob = `${reasoning || ''}\n${reply || ''}\n${findings}`;
// Do not require file paths / symbol names in the public reply (that reads as
// AI dump). Proof of inspection lives in findings + reasoning only.
const blob = `${reasoning || ''}\n${findings}`;

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Reject code identifiers before posting replies

Because high-confidence classifications are posted unchanged by applyClassification, dropping reply from the grounding check means a classifier response whose public reply still contains AIChatPanelContent.tsx or handleNewChat passes normalization as long as reasoning/code_findings are grounded. The new prompt makes those identifiers hard-forbidden in user-facing replies, but this enforcement path now ignores the reply entirely, so a non-compliant model response will still be published to users; please add a separate reply scrub/reject check instead of only relaxing grounding.

Useful? React with 👍 / 👎.

@github-actions

Copy link
Copy Markdown
Contributor

Automatic fix did not produce additional code changes for the latest Codex findings. Marking for human review.

@github-actions github-actions Bot added the ready-for-human Requires human implementation label Jul 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automation:codex-loop Own/bot PR waiting on Codex review↔fix loop ready-for-human Requires human implementation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant