From 0b119804f0f6fa9d1eb9bee6501e46a6b20b28f9 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Sat, 21 Feb 2026 04:46:13 +0000 Subject: [PATCH 1/2] Add text-beautifier edit levels Add high/low/none edit dimensions for text-beautifier docs and workflow source copy under github/workflows. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- gh-agent-workflows/text-beautifier/README.md | 15 ++ .../text-beautifier/example.yml | 6 + github/workflows/gh-aw-text-beautifier.md | 219 ++++++++++++++++++ 3 files changed, 240 insertions(+) create mode 100644 github/workflows/gh-aw-text-beautifier.md diff --git a/gh-agent-workflows/text-beautifier/README.md b/gh-agent-workflows/text-beautifier/README.md index 6a3b7ea4..5a885907 100644 --- a/gh-agent-workflows/text-beautifier/README.md +++ b/gh-agent-workflows/text-beautifier/README.md @@ -30,6 +30,21 @@ See [example.yml](example.yml) for the full workflow file. | `additional-instructions` | Repo-specific instructions appended to the agent prompt | No | `""` | | `setup-commands` | Shell commands run before the agent starts | No | `""` | | `allowed-bot-users` | Allowlisted bot actor usernames (comma-separated) | No | `github-actions[bot]` | +| `edit-typos` | How aggressively to flag typos and misspellings (`high`/`low`/`none`) | No | `low` | +| `edit-grammar` | How aggressively to flag grammar and sentence construction problems (`high`/`low`/`none`) | No | `low` | +| `edit-clarity` | How aggressively to flag unclear user-facing text (`high`/`low`/`none`) | No | `low` | +| `edit-terminology` | How aggressively to flag inconsistent terminology (`high`/`low`/`none`) | No | `low` | +| `edit-misleading-text` | How aggressively to flag text that conflicts with behavior (`high`/`low`/`none`) | No | `low` | + +### Edit Levels + +Each edit dimension accepts one of three levels: + +| Level | Meaning | +| --- | --- | +| `high` | Apply best judgment proactively within this dimension | +| `low` | Report only concrete, unambiguous problems in this dimension | +| `none` | Skip this dimension entirely | ## Safe Outputs diff --git a/gh-agent-workflows/text-beautifier/example.yml b/gh-agent-workflows/text-beautifier/example.yml index 818eece5..2b3a69f4 100644 --- a/gh-agent-workflows/text-beautifier/example.yml +++ b/gh-agent-workflows/text-beautifier/example.yml @@ -12,5 +12,11 @@ permissions: jobs: run: uses: elastic/ai-github-actions/.github/workflows/gh-aw-text-beautifier.lock.yml@v0 + with: + # edit-typos: low + # edit-grammar: low + # edit-clarity: low + # edit-terminology: low + # edit-misleading-text: low secrets: COPILOT_GITHUB_TOKEN: ${{ secrets.COPILOT_GITHUB_TOKEN }} diff --git a/github/workflows/gh-aw-text-beautifier.md b/github/workflows/gh-aw-text-beautifier.md new file mode 100644 index 00000000..6371cd71 --- /dev/null +++ b/github/workflows/gh-aw-text-beautifier.md @@ -0,0 +1,219 @@ +--- +name: "Text Beautifier" +description: "Find typos, unclear error messages, and awkward user-facing text, then file an improvement issue" +imports: + - gh-aw-fragments/elastic-tools.md + - gh-aw-fragments/runtime-setup.md + - gh-aw-fragments/formatting.md + - gh-aw-fragments/rigor.md + - gh-aw-fragments/mcp-pagination.md + - gh-aw-fragments/messages-footer.md + - gh-aw-fragments/safe-output-create-issue.md + - gh-aw-fragments/scheduled-report.md +engine: + id: copilot + model: gpt-5.3-codex +on: + workflow_call: + inputs: + additional-instructions: + description: "Repo-specific instructions appended to the agent prompt" + type: string + required: false + default: "" + setup-commands: + description: "Shell commands to run before the agent starts (dependency install, build, etc.)" + type: string + required: false + default: "" + allowed-bot-users: + description: "Allowlisted bot actor usernames (comma-separated)" + type: string + required: false + default: "github-actions[bot]" + messages-footer: + description: "Footer appended to all agent comments and reviews" + type: string + required: false + default: "" + edit-typos: + description: "How aggressively to flag typos and misspellings. 'high' = suggest broad consistency fixes, 'low' = flag only clear spelling errors, 'none' = skip typo checks" + type: string + required: false + default: "low" + edit-grammar: + description: "How aggressively to flag grammar and sentence construction problems. 'high' = improve awkward sentence structure, 'low' = flag only clear grammatical errors, 'none' = skip grammar checks" + type: string + required: false + default: "low" + edit-clarity: + description: "How aggressively to flag unclear user-facing text, especially error/help messages. 'high' = proactively suggest clearer phrasing, 'low' = flag only clearly ambiguous text, 'none' = skip clarity checks" + type: string + required: false + default: "low" + edit-terminology: + description: "How aggressively to flag inconsistent terminology for the same concept. 'high' = proactively normalize wording, 'low' = flag only unambiguous inconsistencies, 'none' = skip terminology checks" + type: string + required: false + default: "low" + edit-misleading-text: + description: "How aggressively to flag text that conflicts with current behavior. 'high' = proactively flag likely drift, 'low' = flag only direct contradictions, 'none' = skip behavior-alignment checks" + type: string + required: false + default: "low" + secrets: + COPILOT_GITHUB_TOKEN: + required: true + roles: [admin, maintainer, write] + bots: + - "${{ inputs.allowed-bot-users }}" +concurrency: + group: text-beautifier + cancel-in-progress: true +permissions: + contents: read + issues: read + pull-requests: read +tools: + github: + toolsets: [repos, issues, pull_requests, search, labels] + bash: true + web-fetch: +network: + allowed: + - defaults + - github + - go + - node + - python + - ruby +strict: false +safe-outputs: + noop: + create-issue: + max: 1 + title-prefix: "[text-beautifier] " + close-older-issues: true + expires: 7d +timeout-minutes: 90 +steps: + - name: Repo-specific setup + if: ${{ inputs.setup-commands != '' }} + env: + SETUP_COMMANDS: ${{ inputs.setup-commands }} + run: eval "$SETUP_COMMANDS" +--- + +Find typos, unclear error messages, and awkward user-facing text that are low-effort to fix, and file a single improvement issue. + +**The bar is high: only report concrete, unambiguous text problems.** Most runs should end with `noop` — that means user-facing text is clean. + +## Edit Level Configuration + +The following edit levels are configured for this run. Each dimension is independent. + +| Dimension | Level | Meaning | +| --- | --- | --- | +| **typos** | `${{ inputs.edit-typos }}` | How aggressively to flag typos and misspellings | +| **grammar** | `${{ inputs.edit-grammar }}` | How aggressively to flag grammar and sentence construction issues | +| **clarity** | `${{ inputs.edit-clarity }}` | How aggressively to flag unclear user-facing text | +| **terminology** | `${{ inputs.edit-terminology }}` | How aggressively to flag inconsistent naming for the same concept | +| **misleading-text** | `${{ inputs.edit-misleading-text }}` | How aggressively to flag text that no longer matches behavior | + +Level semantics: +- **`high`** — apply best judgment proactively within this dimension +- **`low`** — report only concrete, unambiguous issues +- **`none`** — skip this dimension entirely + +### Data Gathering + +1. Call `generate_agents_md` to get repository conventions. If it fails, continue. +2. Identify user-facing text sources — scan the repository for: + - CLI output strings, error messages, and help text + - Log messages shown to users (not debug-level internal logs) + - README, CONTRIBUTING, DEVELOPING, and other markdown documentation + - UI strings, notification templates, and user-visible configuration descriptions + - Code comments in public APIs that appear in generated documentation +3. Read the identified files and search for text issues. + +### What to Look For by Dimension + +Use each dimension's configured level to determine whether to report findings. + +#### Typos (`${{ inputs.edit-typos }}`) + +- **`high`**: Flag typos/misspellings proactively and include nearby consistency fixes when they are obviously beneficial. +- **`low`**: Flag only clear spelling errors (for example, `recieve` → `receive`), not style variants. +- **`none`**: Skip typo checks. + +#### Grammar (`${{ inputs.edit-grammar }}`) + +- **`high`**: Flag grammar and sentence construction issues that reduce readability, including awkward or fragmented sentences. +- **`low`**: Flag only clear grammatical errors (subject-verb disagreement, missing articles, broken sentence structure). +- **`none`**: Skip grammar checks. + +#### Clarity (`${{ inputs.edit-clarity }}`) + +- **`high`**: Proactively flag unclear user-facing text and suggest concrete rewrites, especially for errors/help text. +- **`low`**: Flag only clearly ambiguous or incomplete user-facing text (for example, `"Error: failed"` with no actionable context). +- **`none`**: Skip clarity checks. + +#### Terminology (`${{ inputs.edit-terminology }}`) + +- **`high`**: Proactively flag inconsistent naming for the same concept across user-facing surfaces. +- **`low`**: Flag only unambiguous inconsistencies where the same concept is clearly referred to by different terms. +- **`none`**: Skip terminology checks. + +#### Misleading Text (`${{ inputs.edit-misleading-text }}`) + +- **`high`**: Proactively flag text likely to have drifted from behavior. +- **`low`**: Flag only direct, verifiable contradictions between text and current code behavior. +- **`none`**: Skip behavior-alignment checks. + +### What to Skip + +- **Style preferences** — do not flag Oxford comma usage, line length, or prose style unless it causes ambiguity +- **Internal-only text** — debug logs, developer-only comments, test fixtures +- **Intentional abbreviations** — short forms that are standard in the project +- **Generated or vendored files** — do not scan auto-generated code, lock files, or third-party content +- **Issues already tracked** — check open issues before filing +- **Findings that require design decisions** — if fixing the text requires deciding on new terminology or restructuring content, skip it + +### Quality Gate — When to Noop + +Call `noop` if any of these are true: +- All edit dimensions are set to `none` +- No concrete text problems were found +- All findings are style preferences rather than clear errors +- The problems found are in generated or vendored files +- A similar issue is already open +- The fixes would require design decisions or significant rewording beyond simple corrections + +### Issue Format + +**Issue title:** Brief summary of text improvements found + +**Issue body:** + +> ## Text Improvements +> +> The following user-facing text issues were found in the repository. Each is a low-effort fix. +> +> ### 1. [Brief description] +> +> **File:** `path/to/file` (line N) +> **Current text:** `the existing text with the problem` +> **Suggested fix:** `the corrected text` +> **Why:** [Brief explanation — typo, grammar, unclear error, etc.] +> +> ### 2. [Next finding...] +> +> ## Suggested Actions +> +> - [ ] [Specific, actionable checkbox for each fix] + +### Labeling + +- If the `text-beautifier` label exists (check with `github-get_label`), include it in the `create_issue` call; otherwise, rely on the `[text-beautifier]` title prefix only. + +${{ inputs.additional-instructions }} From 67e9e34136809792dd7021d31e39e3f9c2977096 Mon Sep 17 00:00:00 2001 From: William Easton Date: Fri, 20 Feb 2026 22:54:04 -0600 Subject: [PATCH 2/2] Move agent output from github/ to .github/ --- .github/workflows/gh-aw-text-beautifier.md | 82 +++++++- github/workflows/gh-aw-text-beautifier.md | 219 --------------------- 2 files changed, 74 insertions(+), 227 deletions(-) delete mode 100644 github/workflows/gh-aw-text-beautifier.md diff --git a/.github/workflows/gh-aw-text-beautifier.md b/.github/workflows/gh-aw-text-beautifier.md index dbfd5c93..6371cd71 100644 --- a/.github/workflows/gh-aw-text-beautifier.md +++ b/.github/workflows/gh-aw-text-beautifier.md @@ -36,6 +36,31 @@ on: type: string required: false default: "" + edit-typos: + description: "How aggressively to flag typos and misspellings. 'high' = suggest broad consistency fixes, 'low' = flag only clear spelling errors, 'none' = skip typo checks" + type: string + required: false + default: "low" + edit-grammar: + description: "How aggressively to flag grammar and sentence construction problems. 'high' = improve awkward sentence structure, 'low' = flag only clear grammatical errors, 'none' = skip grammar checks" + type: string + required: false + default: "low" + edit-clarity: + description: "How aggressively to flag unclear user-facing text, especially error/help messages. 'high' = proactively suggest clearer phrasing, 'low' = flag only clearly ambiguous text, 'none' = skip clarity checks" + type: string + required: false + default: "low" + edit-terminology: + description: "How aggressively to flag inconsistent terminology for the same concept. 'high' = proactively normalize wording, 'low' = flag only unambiguous inconsistencies, 'none' = skip terminology checks" + type: string + required: false + default: "low" + edit-misleading-text: + description: "How aggressively to flag text that conflicts with current behavior. 'high' = proactively flag likely drift, 'low' = flag only direct contradictions, 'none' = skip behavior-alignment checks" + type: string + required: false + default: "low" secrets: COPILOT_GITHUB_TOKEN: required: true @@ -83,6 +108,23 @@ Find typos, unclear error messages, and awkward user-facing text that are low-ef **The bar is high: only report concrete, unambiguous text problems.** Most runs should end with `noop` — that means user-facing text is clean. +## Edit Level Configuration + +The following edit levels are configured for this run. Each dimension is independent. + +| Dimension | Level | Meaning | +| --- | --- | --- | +| **typos** | `${{ inputs.edit-typos }}` | How aggressively to flag typos and misspellings | +| **grammar** | `${{ inputs.edit-grammar }}` | How aggressively to flag grammar and sentence construction issues | +| **clarity** | `${{ inputs.edit-clarity }}` | How aggressively to flag unclear user-facing text | +| **terminology** | `${{ inputs.edit-terminology }}` | How aggressively to flag inconsistent naming for the same concept | +| **misleading-text** | `${{ inputs.edit-misleading-text }}` | How aggressively to flag text that no longer matches behavior | + +Level semantics: +- **`high`** — apply best judgment proactively within this dimension +- **`low`** — report only concrete, unambiguous issues +- **`none`** — skip this dimension entirely + ### Data Gathering 1. Call `generate_agents_md` to get repository conventions. If it fails, continue. @@ -94,16 +136,39 @@ Find typos, unclear error messages, and awkward user-facing text that are low-ef - Code comments in public APIs that appear in generated documentation 3. Read the identified files and search for text issues. -### What to Look For +### What to Look For by Dimension + +Use each dimension's configured level to determine whether to report findings. + +#### Typos (`${{ inputs.edit-typos }}`) + +- **`high`**: Flag typos/misspellings proactively and include nearby consistency fixes when they are obviously beneficial. +- **`low`**: Flag only clear spelling errors (for example, `recieve` → `receive`), not style variants. +- **`none`**: Skip typo checks. + +#### Grammar (`${{ inputs.edit-grammar }}`) + +- **`high`**: Flag grammar and sentence construction issues that reduce readability, including awkward or fragmented sentences. +- **`low`**: Flag only clear grammatical errors (subject-verb disagreement, missing articles, broken sentence structure). +- **`none`**: Skip grammar checks. + +#### Clarity (`${{ inputs.edit-clarity }}`) + +- **`high`**: Proactively flag unclear user-facing text and suggest concrete rewrites, especially for errors/help text. +- **`low`**: Flag only clearly ambiguous or incomplete user-facing text (for example, `"Error: failed"` with no actionable context). +- **`none`**: Skip clarity checks. + +#### Terminology (`${{ inputs.edit-terminology }}`) + +- **`high`**: Proactively flag inconsistent naming for the same concept across user-facing surfaces. +- **`low`**: Flag only unambiguous inconsistencies where the same concept is clearly referred to by different terms. +- **`none`**: Skip terminology checks. -Focus on **concrete, unambiguous problems** in user-facing text: +#### Misleading Text (`${{ inputs.edit-misleading-text }}`) -1. **Typos and misspellings** — real spelling errors, not style preferences (e.g., `recieve` → `receive`, `occurence` → `occurrence`) -2. **Grammatical errors** — subject-verb disagreement, missing articles, broken sentences -3. **Unclear error messages** — errors that do not tell the user what went wrong or what to do next (e.g., `"Error: failed"` with no context) -4. **Inconsistent terminology** — the same concept referred to by different names in different places (e.g., `workspace` vs `project` vs `repo` for the same thing) -5. **Broken or incomplete sentences** — truncated messages, dangling phrases, copy-paste artifacts -6. **Misleading text** — messages that describe behavior that no longer matches the code +- **`high`**: Proactively flag text likely to have drifted from behavior. +- **`low`**: Flag only direct, verifiable contradictions between text and current code behavior. +- **`none`**: Skip behavior-alignment checks. ### What to Skip @@ -117,6 +182,7 @@ Focus on **concrete, unambiguous problems** in user-facing text: ### Quality Gate — When to Noop Call `noop` if any of these are true: +- All edit dimensions are set to `none` - No concrete text problems were found - All findings are style preferences rather than clear errors - The problems found are in generated or vendored files diff --git a/github/workflows/gh-aw-text-beautifier.md b/github/workflows/gh-aw-text-beautifier.md deleted file mode 100644 index 6371cd71..00000000 --- a/github/workflows/gh-aw-text-beautifier.md +++ /dev/null @@ -1,219 +0,0 @@ ---- -name: "Text Beautifier" -description: "Find typos, unclear error messages, and awkward user-facing text, then file an improvement issue" -imports: - - gh-aw-fragments/elastic-tools.md - - gh-aw-fragments/runtime-setup.md - - gh-aw-fragments/formatting.md - - gh-aw-fragments/rigor.md - - gh-aw-fragments/mcp-pagination.md - - gh-aw-fragments/messages-footer.md - - gh-aw-fragments/safe-output-create-issue.md - - gh-aw-fragments/scheduled-report.md -engine: - id: copilot - model: gpt-5.3-codex -on: - workflow_call: - inputs: - additional-instructions: - description: "Repo-specific instructions appended to the agent prompt" - type: string - required: false - default: "" - setup-commands: - description: "Shell commands to run before the agent starts (dependency install, build, etc.)" - type: string - required: false - default: "" - allowed-bot-users: - description: "Allowlisted bot actor usernames (comma-separated)" - type: string - required: false - default: "github-actions[bot]" - messages-footer: - description: "Footer appended to all agent comments and reviews" - type: string - required: false - default: "" - edit-typos: - description: "How aggressively to flag typos and misspellings. 'high' = suggest broad consistency fixes, 'low' = flag only clear spelling errors, 'none' = skip typo checks" - type: string - required: false - default: "low" - edit-grammar: - description: "How aggressively to flag grammar and sentence construction problems. 'high' = improve awkward sentence structure, 'low' = flag only clear grammatical errors, 'none' = skip grammar checks" - type: string - required: false - default: "low" - edit-clarity: - description: "How aggressively to flag unclear user-facing text, especially error/help messages. 'high' = proactively suggest clearer phrasing, 'low' = flag only clearly ambiguous text, 'none' = skip clarity checks" - type: string - required: false - default: "low" - edit-terminology: - description: "How aggressively to flag inconsistent terminology for the same concept. 'high' = proactively normalize wording, 'low' = flag only unambiguous inconsistencies, 'none' = skip terminology checks" - type: string - required: false - default: "low" - edit-misleading-text: - description: "How aggressively to flag text that conflicts with current behavior. 'high' = proactively flag likely drift, 'low' = flag only direct contradictions, 'none' = skip behavior-alignment checks" - type: string - required: false - default: "low" - secrets: - COPILOT_GITHUB_TOKEN: - required: true - roles: [admin, maintainer, write] - bots: - - "${{ inputs.allowed-bot-users }}" -concurrency: - group: text-beautifier - cancel-in-progress: true -permissions: - contents: read - issues: read - pull-requests: read -tools: - github: - toolsets: [repos, issues, pull_requests, search, labels] - bash: true - web-fetch: -network: - allowed: - - defaults - - github - - go - - node - - python - - ruby -strict: false -safe-outputs: - noop: - create-issue: - max: 1 - title-prefix: "[text-beautifier] " - close-older-issues: true - expires: 7d -timeout-minutes: 90 -steps: - - name: Repo-specific setup - if: ${{ inputs.setup-commands != '' }} - env: - SETUP_COMMANDS: ${{ inputs.setup-commands }} - run: eval "$SETUP_COMMANDS" ---- - -Find typos, unclear error messages, and awkward user-facing text that are low-effort to fix, and file a single improvement issue. - -**The bar is high: only report concrete, unambiguous text problems.** Most runs should end with `noop` — that means user-facing text is clean. - -## Edit Level Configuration - -The following edit levels are configured for this run. Each dimension is independent. - -| Dimension | Level | Meaning | -| --- | --- | --- | -| **typos** | `${{ inputs.edit-typos }}` | How aggressively to flag typos and misspellings | -| **grammar** | `${{ inputs.edit-grammar }}` | How aggressively to flag grammar and sentence construction issues | -| **clarity** | `${{ inputs.edit-clarity }}` | How aggressively to flag unclear user-facing text | -| **terminology** | `${{ inputs.edit-terminology }}` | How aggressively to flag inconsistent naming for the same concept | -| **misleading-text** | `${{ inputs.edit-misleading-text }}` | How aggressively to flag text that no longer matches behavior | - -Level semantics: -- **`high`** — apply best judgment proactively within this dimension -- **`low`** — report only concrete, unambiguous issues -- **`none`** — skip this dimension entirely - -### Data Gathering - -1. Call `generate_agents_md` to get repository conventions. If it fails, continue. -2. Identify user-facing text sources — scan the repository for: - - CLI output strings, error messages, and help text - - Log messages shown to users (not debug-level internal logs) - - README, CONTRIBUTING, DEVELOPING, and other markdown documentation - - UI strings, notification templates, and user-visible configuration descriptions - - Code comments in public APIs that appear in generated documentation -3. Read the identified files and search for text issues. - -### What to Look For by Dimension - -Use each dimension's configured level to determine whether to report findings. - -#### Typos (`${{ inputs.edit-typos }}`) - -- **`high`**: Flag typos/misspellings proactively and include nearby consistency fixes when they are obviously beneficial. -- **`low`**: Flag only clear spelling errors (for example, `recieve` → `receive`), not style variants. -- **`none`**: Skip typo checks. - -#### Grammar (`${{ inputs.edit-grammar }}`) - -- **`high`**: Flag grammar and sentence construction issues that reduce readability, including awkward or fragmented sentences. -- **`low`**: Flag only clear grammatical errors (subject-verb disagreement, missing articles, broken sentence structure). -- **`none`**: Skip grammar checks. - -#### Clarity (`${{ inputs.edit-clarity }}`) - -- **`high`**: Proactively flag unclear user-facing text and suggest concrete rewrites, especially for errors/help text. -- **`low`**: Flag only clearly ambiguous or incomplete user-facing text (for example, `"Error: failed"` with no actionable context). -- **`none`**: Skip clarity checks. - -#### Terminology (`${{ inputs.edit-terminology }}`) - -- **`high`**: Proactively flag inconsistent naming for the same concept across user-facing surfaces. -- **`low`**: Flag only unambiguous inconsistencies where the same concept is clearly referred to by different terms. -- **`none`**: Skip terminology checks. - -#### Misleading Text (`${{ inputs.edit-misleading-text }}`) - -- **`high`**: Proactively flag text likely to have drifted from behavior. -- **`low`**: Flag only direct, verifiable contradictions between text and current code behavior. -- **`none`**: Skip behavior-alignment checks. - -### What to Skip - -- **Style preferences** — do not flag Oxford comma usage, line length, or prose style unless it causes ambiguity -- **Internal-only text** — debug logs, developer-only comments, test fixtures -- **Intentional abbreviations** — short forms that are standard in the project -- **Generated or vendored files** — do not scan auto-generated code, lock files, or third-party content -- **Issues already tracked** — check open issues before filing -- **Findings that require design decisions** — if fixing the text requires deciding on new terminology or restructuring content, skip it - -### Quality Gate — When to Noop - -Call `noop` if any of these are true: -- All edit dimensions are set to `none` -- No concrete text problems were found -- All findings are style preferences rather than clear errors -- The problems found are in generated or vendored files -- A similar issue is already open -- The fixes would require design decisions or significant rewording beyond simple corrections - -### Issue Format - -**Issue title:** Brief summary of text improvements found - -**Issue body:** - -> ## Text Improvements -> -> The following user-facing text issues were found in the repository. Each is a low-effort fix. -> -> ### 1. [Brief description] -> -> **File:** `path/to/file` (line N) -> **Current text:** `the existing text with the problem` -> **Suggested fix:** `the corrected text` -> **Why:** [Brief explanation — typo, grammar, unclear error, etc.] -> -> ### 2. [Next finding...] -> -> ## Suggested Actions -> -> - [ ] [Specific, actionable checkbox for each fix] - -### Labeling - -- If the `text-beautifier` label exists (check with `github-get_label`), include it in the `create_issue` call; otherwise, rely on the `[text-beautifier]` title prefix only. - -${{ inputs.additional-instructions }}