feat: nemoclaw-maintainer-triage skill and shared triage-instructions.md

[wscurran]

Summary

• Adds docs/triage-instructions.md — single source of truth for AI-assisted label triage. Contains role definition, label guide, skip list, comment tier rules, and tone rules. Extracted and formalized from the nvoss-velocity dashboard prompt/label guide so both the CLI skill and the dashboard use identical instructions.
• Adds .agents/skills/nemoclaw-maintainer-triage/ — CLI triage skill for NemoClaw maintainers. Supports single-item mode (give it an issue/PR number) and batch mode (fetches all unlabeled open items). Applies labels and optional triage comments via gh CLI on approval. Logs sessions to ~/development/daily-rhythm/activity/nemoclaw-triage-log.md.

Architecture note

The skill reads docs/triage-instructions.md at runtime via cat. The nvoss-velocity dashboard will fetch the same file from GitHub at generation time (separate PR). This keeps execution paths independent while preventing the labeling logic from drifting between the two environments.

Test plan

• Invoke skill with a specific issue number — confirm it reads triage-instructions.md, suggests labels, applies on approval, logs to activity file
• Invoke skill with no number — confirm batch mode fetches unlabeled items and works through them interactively
• Confirm priority: high is only suggested for genuinely blocking issues
• Confirm bare enhancement is not suggested alongside enhancement: * sub-labels

🤖 Generated with Claude Code

Summary by CodeRabbit

• New Features

  • AI-assisted triage for GitHub issues and PRs with single-item and batch modes (up to 50 items), including batch prioritization.
  • Generates structured suggestions (labels, one-sentence reason, optional comment) and requires user confirmation to apply labels/comments.
  • Records approved actions to a persistent triage log with initialization and session summaries.

• Documentation

  • Added detailed triage instructions, label semantics, selection rules, and comment guidance for consistent categorization.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

📝 Walkthrough

Walkthrough

Adds a new AI-invocable triage skill and a machine-readable triage rules doc; supports single-item or prioritized batch flows to generate label suggestions and optional comments, requires user approval to apply labels/comments via the gh CLI, and appends per-item and batch summaries to a persistent activity log.

Changes

Cohort / File(s)	Summary
Triage Skill .agents/skills/nemoclaw-maintainer-triage/SKILL.md	New user-invocable skill describing runtime flow: read docs/triage-instructions.md, operate in single-item or batch mode (up to 50), emit structured JSON suggestions, prompt user to apply/edit/skip, call gh to add labels/post comments, and append per-item log entries.
Triage Instructions docs/triage-instructions.md	New machine-readable rules: allowed/forbidden labels, 1–5 label constraint, priority restrictions, label semantics, comment tiering (quality_tier vs standard_tier), metadata-driven overrides, and strict JSON-only runtime output schema (results array with number, labels, reason, comment).
Logging & Batch Behavior (described) ~/development/daily-rhythm/activity/nemoclaw-triage-log.md	Describes log initialization if missing, per-item log entry format (identifier/title, date, labels applied, comment posted), and appending a batch-session summary at batch end.

Sequence Diagram

sequenceDiagram
    participant User
    participant Skill as Triage Skill
    participant Docs as "Triage Instructions"
    participant GH as "GitHub CLI"
    participant Log as "Activity Log"

    User->>Skill: Invoke skill (single-item or batch)
    Skill->>Docs: Read live guidance and rules (runtime)
    Docs-->>Skill: Return label definitions & constraints

    alt Single-Item Mode
        User->>Skill: Provide issue/PR number
    else Batch Mode
        Skill->>GH: Query unlabeled open issues/PRs (prioritized, up to 50)
        GH-->>Skill: Return items
    end

    loop For each item
        Skill->>Skill: Generate suggestion (labels, reason, optional comment)
        Skill->>User: Present suggestion and choices (apply/edit/skip/apply-no-comment)
        User->>Skill: Approve / Edit / Skip / Omit comment

        alt Approved
            Skill->>GH: Apply labels via `gh ... edit --add-label`
            GH-->>Skill: Labels applied
            opt Comment approved
                Skill->>GH: Post comment via `gh ... comment`
                GH-->>Skill: Comment posted
            end
            Skill->>Log: Append per-item entry (id/title, date, labels, comment status)
            Log-->>Skill: Confirmed
        else Skipped
            Skill-->>User: Continue to next item
        end
    end

    Skill->>User: Present batch session summary (if batch)

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 I hopped through issues, noses twitching bright,
Read the rules by moon and morning light.
I nudged some labels, left a tiny note,
Logged each hop along my carrot route.
Triage done — a happy, hopping byte. 🥕

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly and clearly summarizes the main changes: adding a new nemoclaw-maintainer-triage skill and a shared triage-instructions.md documentation file, which are the primary deliverables of the PR.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/triage-skill

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 6

🧹 Nitpick comments (1)

docs/triage-instructions.md (1)

14-14: Reduce em-dash density in prose (LLM pattern detected).

There are repeated em-dash constructions across the page; several lines use them where commas/periods would read cleaner and align better with the style rule.

As per coding guidelines, "Excessive em dashes. One per paragraph is fine; multiple per paragraph or em dashes used instead of commas/periods should be flagged."

Also applies to: 21-21, 29-32, 39-40, 47-47, 57-57, 65-67, 80-80, 82-82, 86-87, 110-110, 117-117, 118-119, 125-125

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/triage-instructions.md` at line 14, The sentence "Assign 1–5 labels from
the provided list that best match the content. Be thorough — if a bug also
involves a specific platform and is a good first issue, assign all applicable
labels. Only skip a label if it genuinely does not apply." overuses em-dashes;
edit this sentence (and other occurrences of the em-dash character "—") to
reduce em-dash density by replacing secondary em-dashes with commas or periods
and ensuring no more than one em-dash per paragraph (follow the "Excessive em
dashes. One per paragraph is fine" guideline), updating nearby lines that repeat
the pattern to improve readability and conform to the style rule.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.agents/skills/nemoclaw-maintainer-triage/SKILL.md:
- Line 3: The documentation claim about batch mode in SKILL.md is inaccurate:
the batch-mode description (line with "fetches all unlabeled open items")
conflicts with the implemented listing commands that are hard-capped at 50;
update the SKILL.md description and the related section (lines ~41-46) to either
(A) accurately state the 50-item limit or (B) remove the limit by implementing
pagination in the listing logic (use the gh CLI pagination or iterate API calls)
so batch-mode truly fetches all unlabeled items; mention the chosen approach in
the doc and ensure the trigger wording ("batch mode", "fetches all unlabeled
open items") matches the code behavior.
- Around line 37-49: The batch-mode selection currently filters to items with
zero labels (the jq filter '.labels | length == 0'), which prevents the
prioritization branch that looks for items with the label/value "priority: high"
from ever running; update the Batch mode selection logic in the "Batch mode"
section so it does not exclude labeled items (either remove or loosen the jq
'.labels | length == 0' filter for the gh issue list and gh pr list examples) or
explicitly include a secondary query that fetches labeled high-priority items
before/alongside the unlabeled set, and keep references to the "priority: high"
prioritization step intact so that the branch can execute.
- Line 1: The SKILL.md file is missing the required SPDX license header; add a
single-line SPDX license header at the very top of SKILL.md (for example:
SPDX-License-Identifier: MIT or the project’s chosen identifier) so the file
conforms to the rule for source files (*.md). Ensure the header is the first
non-empty line in the file and matches the project's standard SPDX identifier.

In `@docs/triage-instructions.md`:
- Around line 1-128: The docs build is failing because the "NemoClaw — Triage
Instructions" Markdown document is orphaned (not referenced by any toctree); fix
by adding this document to your Sphinx/Docs toctree (insert a toctree entry that
references "NemoClaw — Triage Instructions" in the site's main index/toctree
page), then re-run the docs preview build to verify the orphan warning is
resolved.
- Around line 1-10: This docs page is missing the required YAML frontmatter; add
a top-of-file frontmatter block containing the fields title, description,
keywords, topics, tags, content type, difficulty, audience, and status with
appropriate values for "NemoClaw — Triage Instructions" so the
`nemoclaw-maintainer-triage` CLI and nvoss-velocity dashboard can parse it;
ensure the block is delimited by --- and populated with concise, valid entries
for each required field.
- Line 1: Add the required SPDX license header as the very first line of the
document "NemoClaw — Triage Instructions" (docs/triage-instructions.md) so it
conforms to the repository rule for source files matching
**/*.{js,ts,tsx,jsx,sh,md}; insert a single-line SPDX header such as
"SPDX-License-Identifier: <LICENSE>" (replace <LICENSE> with the project's SPDX
identifier, e.g., Apache-2.0 or MIT) above the existing title.

---

Nitpick comments:
In `@docs/triage-instructions.md`:
- Line 14: The sentence "Assign 1–5 labels from the provided list that best
match the content. Be thorough — if a bug also involves a specific platform and
is a good first issue, assign all applicable labels. Only skip a label if it
genuinely does not apply." overuses em-dashes; edit this sentence (and other
occurrences of the em-dash character "—") to reduce em-dash density by replacing
secondary em-dashes with commas or periods and ensuring no more than one em-dash
per paragraph (follow the "Excessive em dashes. One per paragraph is fine"
guideline), updating nearby lines that repeat the pattern to improve readability
and conform to the style rule.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 7ae3334c-9f5c-4d6b-88cd-17b95397b4dc

📥 Commits

Reviewing files that changed from the base of the PR and between 211d19f and d9d341d.

📒 Files selected for processing (2)

• .agents/skills/nemoclaw-maintainer-triage/SKILL.md
• docs/triage-instructions.md

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Add SPDX header at file top.

This source markdown file is missing the required SPDX license header.

As per coding guidelines, "**/*.{js,ts,tsx,jsx,sh,md}: Include SPDX license header in every source file."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.agents/skills/nemoclaw-maintainer-triage/SKILL.md at line 1, The SKILL.md
file is missing the required SPDX license header; add a single-line SPDX license
header at the very top of SKILL.md (for example: SPDX-License-Identifier: MIT or
the project’s chosen identifier) so the file conforms to the rule for source
files (*.md). Ensure the header is the first non-empty line in the file and
matches the project's standard SPDX identifier.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Prioritization rule is unreachable with current unlabeled-only filter.

Batch mode only selects items with zero labels, but priority step 1 asks to prioritize items that already have priority: high. Those items are excluded earlier, so this branch cannot execute.

Proposed doc fix

-1. Items with `priority: high` already applied (need comment)
+1. Items indicating outage/data-loss/critical breakage in title or body (candidate for `priority: high`)

Also applies to: 139-139

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.agents/skills/nemoclaw-maintainer-triage/SKILL.md around lines 37 - 49, The
batch-mode selection currently filters to items with zero labels (the jq filter
'.labels | length == 0'), which prevents the prioritization branch that looks
for items with the label/value "priority: high" from ever running; update the
Batch mode selection logic in the "Batch mode" section so it does not exclude
labeled items (either remove or loosen the jq '.labels | length == 0' filter for
the gh issue list and gh pr list examples) or explicitly include a secondary
query that fetches labeled high-priority items before/alongside the unlabeled
set, and keep references to the "priority: high" prioritization step intact so
that the branch can execute.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Include this page in a docs toctree to fix preview build failure.

The pipeline error indicates this document is orphaned (document isn't included in any toctree), so docs preview fails until it is referenced from an index/toctree page.

🧰 Tools

🪛 GitHub Actions: Docs PR Preview

[error] 1-1: Warning, treated as error by Sphinx: document isn't included in any toctree

🪛 LanguageTool

[style] ~110-~110: This phrase is redundant. Consider writing “details”.
Context: ...with "Thanks," then naturally reference specific details from the body. Avoid "I've taken a look...

(SPECIFIC_DETAILS)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/triage-instructions.md` around lines 1 - 128, The docs build is failing
because the "NemoClaw — Triage Instructions" Markdown document is orphaned (not
referenced by any toctree); fix by adding this document to your Sphinx/Docs
toctree (insert a toctree entry that references "NemoClaw — Triage Instructions"
in the site's main index/toctree page), then re-run the docs preview build to
verify the orphan warning is resolved.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Add SPDX header at the top of the document.

The file is missing the required SPDX license header.

As per coding guidelines, "**/*.{js,ts,tsx,jsx,sh,md}: Include SPDX license header in every source file."

🧰 Tools

🪛 GitHub Actions: Docs PR Preview

[error] 1-1: Warning, treated as error by Sphinx: document isn't included in any toctree

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/triage-instructions.md` at line 1, Add the required SPDX license header
as the very first line of the document "NemoClaw — Triage Instructions"
(docs/triage-instructions.md) so it conforms to the repository rule for source
files matching **/*.{js,ts,tsx,jsx,sh,md}; insert a single-line SPDX header such
as "SPDX-License-Identifier: <LICENSE>" (replace <LICENSE> with the project's
SPDX identifier, e.g., Apache-2.0 or MIT) above the existing title.

[coderabbitai]

Actionable comments posted: 1

♻️ Duplicate comments (1)

docs/triage-instructions.md (1)

1-5: ⚠️ Potential issue | 🟠 Major

Add required frontmatter fields and SPDX header at the top.

Line 1-Line 5 still lacks the required docs metadata block (title, description, keywords, topics, tags, content type, difficulty, audience, status) and an SPDX license header after frontmatter.

Proposed patch

 ---
+title:
+  page: NemoClaw Triage Instructions
+description: Canonical AI-assisted label triage rules for NemoClaw issues and pull requests.
+keywords: [NemoClaw, triage, labels, GitHub, maintainer]
+topics: [maintenance, triage]
+tags: [docs, triage]
+content type: reference
+difficulty: intermediate
+audience: maintainers
+status: active
 orphan: true
 ---
+
+SPDX-License-Identifier: Apache-2.0

As per coding guidelines, "Frontmatter includes title, description, keywords, topics, tags, content type, difficulty, audience, and status fields." and "**/*.{js,ts,tsx,jsx,sh,md}: Include SPDX license header in every source file."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/triage-instructions.md` around lines 1 - 5, The file
docs/triage-instructions.md is missing the required YAML frontmatter and an SPDX
license header; add a top YAML block containing the fields title, description,
keywords, topics, tags, content type, difficulty, audience, and status (populate
with appropriate values for this doc) immediately after the leading --- and then
add an SPDX license header (e.g., // SPDX-License-Identifier: MIT or a Markdown
comment variant) directly after the frontmatter; ensure the frontmatter block
and SPDX header appear before any content (the existing "# NemoClaw — Triage
Instructions") so the parser and license scanner detect them.

🧹 Nitpick comments (1)

docs/triage-instructions.md (1)

114-129: Reduce em-dash density in long guidance lines (LLM pattern detected).

Line 114 and Line 129 each use multiple em dashes in one paragraph; split into shorter sentences or use commas/periods instead.

As per coding guidelines, "Excessive em dashes. One per paragraph is fine; multiple per paragraph or em dashes used instead of commas/periods should be flagged."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/triage-instructions.md` around lines 114 - 129, The two paragraphs under
the "quality_tier" bullet and the "Tone Rules" list have excessive em-dash
usage; edit the docs/triage-instructions.md content for the "**quality_tier**
(influencer author, company-affiliated author, or body > 800 chars):" bullet and
the related Tone Rules lines to remove multiple em dashes per paragraph by
splitting long sentences into shorter sentences and/or replacing extra em dashes
with commas or periods so each paragraph uses at most one em dash and reads
naturally.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/triage-instructions.md`:
- Around line 108-132: The document ending lacks the required terminal "Next
Steps" section; add a final level-2 header titled "Next Steps" at the bottom of
docs/triage-instructions.md and include a short bulleted list of relevant
internal links (e.g., linking to "Comment Tiers", "Tone Rules", contributing or
page-structure guidelines) so readers can navigate to related pages; ensure the
header text exactly matches "Next Steps" and the links use the same relative
markdown link style as the rest of the file and appear after the existing
content (as the last section).

---

Duplicate comments:
In `@docs/triage-instructions.md`:
- Around line 1-5: The file docs/triage-instructions.md is missing the required
YAML frontmatter and an SPDX license header; add a top YAML block containing the
fields title, description, keywords, topics, tags, content type, difficulty,
audience, and status (populate with appropriate values for this doc) immediately
after the leading --- and then add an SPDX license header (e.g., //
SPDX-License-Identifier: MIT or a Markdown comment variant) directly after the
frontmatter; ensure the frontmatter block and SPDX header appear before any
content (the existing "# NemoClaw — Triage Instructions") so the parser and
license scanner detect them.

---

Nitpick comments:
In `@docs/triage-instructions.md`:
- Around line 114-129: The two paragraphs under the "quality_tier" bullet and
the "Tone Rules" list have excessive em-dash usage; edit the
docs/triage-instructions.md content for the "**quality_tier** (influencer
author, company-affiliated author, or body > 800 chars):" bullet and the related
Tone Rules lines to remove multiple em dashes per paragraph by splitting long
sentences into shorter sentences and/or replacing extra em dashes with commas or
periods so each paragraph uses at most one em dash and reads naturally.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: e95ded72-6b81-480e-a6ce-e9916d6d9352

📥 Commits

Reviewing files that changed from the base of the PR and between d9d341d and ad25aeb.

📒 Files selected for processing (1)

• docs/triage-instructions.md

[coderabbitai]

Actionable comments posted: 2

🧹 Nitpick comments (1)

docs/triage-instructions.md (1)

3-3: Align the H1 with the frontmatter title value.

The H1 text and frontmatter title are not identical right now. Keep them exactly matched for docs consistency.

As per coding guidelines, "H1 heading matches the title.page frontmatter value."

Also applies to: 16-16

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/triage-instructions.md` at line 3, The H1 in docs/triage-instructions.md
must exactly match the frontmatter title.page value; update the top-level
markdown H1 header to read "NemoClaw Triage Instructions" (matching the
frontmatter title) so the H1 heading and the frontmatter title.page are
identical; ensure there are no extra whitespace, punctuation or casing
differences.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/triage-instructions.md`:
- Around line 1-11: The YAML frontmatter is missing the required difficulty
field; open the top YAML block (the --- delimited frontmatter containing title,
description, keywords, topics, tags, content_type, audience, status) and add a
difficulty entry (e.g., difficulty: beginner|intermediate|advanced) so the
frontmatter includes title, description, keywords, topics, tags, content_type,
difficulty, audience, and status; ensure the new difficulty line follows YAML
formatting and is inside the existing --- frontmatter block.
- Around line 149-150: The two local links "Maintainer Guide"
(maintainer-guide.md) and "Project Workflow" (project-workflow.md) are broken in
CI; update them to Sphinx-friendly references or correct relative paths so docs
build passes. Replace the markdown file links with Sphinx doc roles (e.g.,
:doc:`maintainer-guide` and :doc:`project-workflow`) or adjust the hrefs to the
correct relative locations where those files live, ensuring the link targets
exactly match the Sphinx source filenames used by the build.

---

Nitpick comments:
In `@docs/triage-instructions.md`:
- Line 3: The H1 in docs/triage-instructions.md must exactly match the
frontmatter title.page value; update the top-level markdown H1 header to read
"NemoClaw Triage Instructions" (matching the frontmatter title) so the H1
heading and the frontmatter title.page are identical; ensure there are no extra
whitespace, punctuation or casing differences.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 88faeb17-0b4b-4403-9ba4-1519b6c89e58

📥 Commits

Reviewing files that changed from the base of the PR and between ad25aeb and 3b75c3a.

📒 Files selected for processing (2)

• .agents/skills/nemoclaw-maintainer-triage/SKILL.md
• docs/triage-instructions.md

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Fix broken Next Steps links to restore docs checks.

Both local links currently resolve as broken in CI (maintainer-guide.md, project-workflow.md), and Sphinx treats this as an error.

As per coding guidelines, "Missing SPDX header, broken cross-references, or incorrect code block language: flag as issues."

🧰 Tools

🪛 GitHub Actions: Docs Links PR

[error] 149-149: check-docs (links): broken local link to 'maintainer-guide.md'.

---

[error] 150-150: check-docs (links): broken local link to 'project-workflow.md'.

🪛 GitHub Actions: Docs PR Preview

[error] 149-149: Sphinx (myst) treated as error: cross-reference target not found: 'maintainer-guide.md' (Warning, treated as error)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/triage-instructions.md` around lines 149 - 150, The two local links
"Maintainer Guide" (maintainer-guide.md) and "Project Workflow"
(project-workflow.md) are broken in CI; update them to Sphinx-friendly
references or correct relative paths so docs build passes. Replace the markdown
file links with Sphinx doc roles (e.g., :doc:`maintainer-guide` and
:doc:`project-workflow`) or adjust the hrefs to the correct relative locations
where those files live, ensuring the link targets exactly match the Sphinx
source filenames used by the build.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (2)

docs/triage-instructions.md (2)

125-125: Split sentences onto separate lines and simplify phrasing.

Line 125 contains three sentences on a single line, which reduces diff readability. Additionally, "specific details" is redundant.

♻️ Proposed fix

-- **quality_tier** (influencer author, company-affiliated author, or body > 800 chars): Write 2–3 sentences. Start with "Thanks," then naturally reference specific details from the body. Avoid "I've taken a look at", "I've reviewed", "it appears to", "I can see that" — these sound bot-generated. Write like a human maintainer giving a warm, specific response.
+- **quality_tier** (influencer author, company-affiliated author, or body > 800 chars): Write 2–3 sentences.
+Start with "Thanks," then naturally reference details from the body.
+Avoid "I've taken a look at", "I've reviewed", "it appears to", "I can see that" — these sound bot-generated.
+Write like a human maintainer giving a warm, specific response.

As per coding guidelines, "One sentence per line in source (makes diffs readable). Flag paragraphs where multiple sentences appear on the same line."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/triage-instructions.md` at line 125, Update the **quality_tier**
guideline line to use one sentence per line and simplify wording by removing the
redundant phrase "specific details"; e.g., split the three sentences into
separate lines, keep "Write 2–3 sentences." on its own line, put "Start with
'Thanks,' then reference details from the body." on the next line, and put the
prohibition list ("Avoid 'I've taken a look at', ...") on its own line; ensure
it still instructs to "Write like a human maintainer giving a warm, specific
response."

---

140-140: Split sentences onto separate lines.

Line 140 contains two sentences on a single line, reducing diff readability.

♻️ Proposed fix

-- Do NOT open with praise about detail or thoroughness. Only reference the quality of the report if the body is genuinely exceptional — multiple reproduction steps, version info, logs, and clear expected vs actual behavior. For most reports, skip the praise entirely and go straight to the triage acknowledgment.
+- Do NOT open with praise about detail or thoroughness.
+Only reference the quality of the report if the body is genuinely exceptional — multiple reproduction steps, version info, logs, and clear expected vs actual behavior.
+For most reports, skip the praise entirely and go straight to the triage acknowledgment.

As per coding guidelines, "One sentence per line in source (makes diffs readable). Flag paragraphs where multiple sentences appear on the same line."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/triage-instructions.md` at line 140, The line containing "Do NOT open
with praise about detail or thoroughness. Only reference the quality of the
report..." should be split so each sentence is on its own line to improve diff
readability; edit the text in docs/triage-instructions.md (the sentence starting
"Do NOT open with praise..." and the following sentence starting "Only reference
the quality...") so they become two separate lines, preserving punctuation and
meaning, and ensure the file follows the "one sentence per line" guideline for
similar paragraph entries.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/triage-instructions.md`:
- Around line 1-11: Add the missing required frontmatter key "difficulty" to the
YAML frontmatter block at the top of the document; update the frontmatter (the
existing keys like title, description, keywords, topics, tags, content_type,
audience, and status) to include a difficulty entry with an appropriate value
(e.g., "beginner", "intermediate", or "advanced") so the document conforms to
the docs structure requirements and the nemoclaw-maintainer-triage CLI/dashboard
ingestion.

---

Nitpick comments:
In `@docs/triage-instructions.md`:
- Line 125: Update the **quality_tier** guideline line to use one sentence per
line and simplify wording by removing the redundant phrase "specific details";
e.g., split the three sentences into separate lines, keep "Write 2–3 sentences."
on its own line, put "Start with 'Thanks,' then reference details from the
body." on the next line, and put the prohibition list ("Avoid 'I've taken a look
at', ...") on its own line; ensure it still instructs to "Write like a human
maintainer giving a warm, specific response."
- Line 140: The line containing "Do NOT open with praise about detail or
thoroughness. Only reference the quality of the report..." should be split so
each sentence is on its own line to improve diff readability; edit the text in
docs/triage-instructions.md (the sentence starting "Do NOT open with praise..."
and the following sentence starting "Only reference the quality...") so they
become two separate lines, preserving punctuation and meaning, and ensure the
file follows the "one sentence per line" guideline for similar paragraph
entries.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 6988005a-5800-4fbd-b8ce-e5542c8e257f

📥 Commits

Reviewing files that changed from the base of the PR and between 3b75c3a and 128323d.

📒 Files selected for processing (1)

• docs/triage-instructions.md

[coderabbitai]

♻️ Duplicate comments (1)

docs/triage-instructions.md (1)

1-11: ⚠️ Potential issue | 🟠 Major

Add the missing difficulty frontmatter field.

The docs frontmatter is still missing difficulty, which is required for docs/**/*.md pages.

Proposed fix

 ---
 orphan: true
 title: "NemoClaw Triage Instructions"
 description: "AI-assisted label triage instructions for NVIDIA/NemoClaw issues and PRs. Single source of truth for the nemoclaw-maintainer-triage CLI skill and the nvoss-velocity dashboard."
 keywords: triage, labels, issues, pull requests, maintainer
 topics: [maintainer, triage, labels]
 tags: [maintainer, triage]
 content_type: reference
+difficulty: advanced
 audience: maintainers
 status: active
 ---

As per coding guidelines, "Frontmatter includes title, description, keywords, topics, tags, content type, difficulty, audience, and status fields."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/triage-instructions.md` around lines 1 - 11, The frontmatter block at
the top of the document is missing the required "difficulty" field; update the
YAML frontmatter (the leading --- block containing title, description, keywords,
topics, tags, content_type, audience, status) to include a difficulty key (e.g.,
difficulty: beginner|intermediate|advanced) appropriate for the page so it
conforms to the docs frontmatter schema.

🧹 Nitpick comments (1)

docs/triage-instructions.md (1)

3-16: Align the H1 text with the frontmatter title exactly.

title and the H1 currently differ (NemoClaw Triage Instructions vs NemoClaw — Triage Instructions). Keep them identical to satisfy page-structure consistency.

As per coding guidelines, "H1 heading matches the title.page frontmatter value."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/triage-instructions.md` around lines 3 - 16, Update the document so the
H1 heading exactly matches the frontmatter title value "NemoClaw Triage
Instructions": change the H1 text currently reading "NemoClaw — Triage
Instructions" to "NemoClaw Triage Instructions" so the frontmatter `title` and
the H1 are identical; ensure no extra punctuation or em dash remains and
preserve the rest of the content and frontmatter unchanged.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In `@docs/triage-instructions.md`:
- Around line 1-11: The frontmatter block at the top of the document is missing
the required "difficulty" field; update the YAML frontmatter (the leading ---
block containing title, description, keywords, topics, tags, content_type,
audience, status) to include a difficulty key (e.g., difficulty:
beginner|intermediate|advanced) appropriate for the page so it conforms to the
docs frontmatter schema.

---

Nitpick comments:
In `@docs/triage-instructions.md`:
- Around line 3-16: Update the document so the H1 heading exactly matches the
frontmatter title value "NemoClaw Triage Instructions": change the H1 text
currently reading "NemoClaw — Triage Instructions" to "NemoClaw Triage
Instructions" so the frontmatter `title` and the H1 are identical; ensure no
extra punctuation or em dash remains and preserve the rest of the content and
frontmatter unchanged.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: a05e08f5-be63-4a9e-8666-500b3eaadce7

📥 Commits

Reviewing files that changed from the base of the PR and between 128323d and e7d9fdf.

📒 Files selected for processing (1)

• docs/triage-instructions.md

[cv]

Still some nits from coderabbit, but none blocking imho