Skip to content

[text-auditor] Fix script help-text drift and grammar in issue-triage prompt examples #1822

Description

@github-actions

Text Improvements

The following user-facing text issues were found in the repository. Each is a low-effort fix.

1. pr-existing-comments.sh usage line conflicts with actual default behavior

File: claude-workflows/pr-review/scripts/pr-existing-comments.sh (line 5)
Current text: # pr-existing-comments.sh - Show all review threads with full details
Suggested fix: # pr-existing-comments.sh - Show all review threads (truncated text by default)
Why: The script truncates comment bodies unless --full is passed, so “full details” is misleading.

2. Unknown-argument error omits an accepted flag

File: scripts/trigger-ci-workflows.sh (line 76)
Current text: Unknown argument: $arg (expected: detectors, fixers, monitors, --dry-run, --list)
Suggested fix: Unknown argument: $arg (expected: detectors, fixers, monitors, --dry-run, --list, --help)
Why: --help/-h is accepted by argument parsing but omitted from the expected-arguments hint.

3. Comma splice in response-writing guidance (same text in both variants)

File: claude-workflows/issue-triage/ro/action.yml (line 146)
Current text: When formulating your response, you will never "bury the lede", you will always provide a clear and concise tl;dr as the first thing in your response.
Suggested fix: When formulating your response, you will never "bury the lede"; you will always provide a clear and concise tl;dr as the first thing in your response.
Why: Two independent clauses are joined with a comma, reducing readability in core user instructions.

File: claude-workflows/issue-triage/rwx/action.yml (line 165)
Current text: When formulating your response, you will never "bury the lede", you will always provide a clear and concise tl;dr as the first thing in your response.
Suggested fix: When formulating your response, you will never "bury the lede"; you will always provide a clear and concise tl;dr as the first thing in your response.
Why: Same duplicated grammar issue in the RWX variant.

4. Comma splice in recommendation example sentence (same text in both variants)

File: claude-workflows/issue-triage/ro/action.yml (line 151)
Current text: PR #654 already implements the requested feature but is incomplete. The Pull Request is not in a mergeable state yet, the remaining work should be completed: ...
Suggested fix: PR #654 already implements the requested feature but is incomplete. The Pull Request is not in a mergeable state yet; the remaining work should be completed: ...
Why: Independent clauses are joined by a comma in an example intended to model high-quality user output.

File: claude-workflows/issue-triage/rwx/action.yml (line 170)
Current text: PR #654 already implements the requested feature but is incomplete. The Pull Request is not in a mergeable state yet, the remaining work should be completed: ...
Suggested fix: PR #654 already implements the requested feature but is incomplete. The Pull Request is not in a mergeable state yet; the remaining work should be completed: ...
Why: Same duplicated grammar issue in the RWX variant.

Suggested Actions

  • Update pr-existing-comments.sh usage text to match default truncation behavior.
  • Update trigger-ci-workflows.sh unknown-argument hint to include --help.
  • Fix the duplicated comma splice in the “bury the lede” guidance in both issue-triage variants.
  • Fix the duplicated comma splice in the PR example sentence in both issue-triage variants.

What is this? | From workflow: Trigger Text Auditor

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

  • expires on Aug 20, 2026, 1:46 PM UTC

Activity

  1. github-actions commented on Aug 20, 2026

    @github-actions
    ContributorAuthor

    This issue was automatically closed because it expired on 2026-08-20T13:46:45.858Z.

    Closed by Workflow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions