Index of every page on this site: llms.txt
All skills
rtk-ai avatar

/pr-triage

@ef0b734
by rtk-airtk-ai/rtk87k stars
5,610
Run it yourself

PR triage: audit open PRs, deep review selected ones, draft and post review comments. Args: "all" to review all, PR numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.

Requires /repo-recap
Use this Skill: https://skilld.dev/gh/rtk-ai/rtk/pr-triage

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

templatesreview-comment.md

≈565 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Review Comment Template

Use this template to generate GitHub PR review comments. Fill in each section based on the code-reviewer agent output. Comments are posted in English (international audience).


Template

## Review

**Scope**: Security, code quality, performance, test coverage, architecture

### Summary

{1–2 sentences: overall assessment. Be direct — what's the main takeaway?}

### Critical Issues 🔴

{List blocking issues that must be fixed before merge. For each:}
{- `file.rs:42` — Description of the problem. Why it matters. Suggested fix.}

{If none: "None found."}

### Important Issues 🟡

{List significant issues that should be fixed. For each:}
{- `file.rs:42` — Description. Why it matters. Suggested fix.}

{If none: "None found."}

### Suggestions 🟢

{List nice-to-haves and minor improvements. For each:}
{- Description. Context. Optional fix.}

{If none: omit this section.}

### What's Good ✅

{Always include at least 1 positive point. Be specific — what works well and why.}
{- Description of what's done right.}

---
*Automated review via [rtk](https://github.com/rtk-ai/rtk) `/pr-triage`*

Formatting Rules

Citation format : file.rs:42 or `code snippet` for inline references

Issue severity :

  • 🔴 Critical : security vulnerability, data loss risk, broken functionality, test missing for new feature
  • 🟡 Important : error handling gap, performance regression, scope creep, missing token savings assertion
  • 🟢 Suggestion : naming, DRY opportunity, documentation, style

RTK-specific checks to mention if relevant :

  • LazyLock<Regex> for fixed patterns reused across calls
  • anyhow::Result + .context("msg") (no bare ?, no .unwrap())
  • Fallback to raw command on filter failure
  • Exit code propagation (std::process::exit(code))
  • Token savings assertion ≥20% in tests
  • Real fixtures (not synthetic test data)
  • No async/tokio dependencies (startup time)

Tone : Professional, constructive, factual. Challenge the code, not the person. No superlatives ("great", "amazing", "perfect"). No filler ("as mentioned", "it's worth noting").

Length : Aim for 200–400 words. Long enough to be useful, short enough to be read.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning1mo4 checks · Risk SAFE
  • Gen Agent Trust Hub1mo

    This skill is a PR triage tool that uses the GitHub CLI to audit and review pull requests. It exhibits a standard indirect prompt injection surface by processing untrusted PR descriptions and code diffs, but it includes manual confirmation steps before taking high-impact actions like posting comments.

  • Socket1mo

    No alerts

  • Snyk1mo

    Risk: MEDIUM · 1 issue

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at ef0b734. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 5 hours ago.

Activeupdated last month
What it can do
Runs commands Reads files
effort
medium
tags
[
  "triage",
  "pr",
  "github",
  "review",
  "code-review",
  "rtk"
]
All 4 allowed tools
BashReadGrepGlob

README badge

README badge for rtk-ai/rtk/pr-triage