Exposed Bug Fix Workflow
JetBrains/Exposed
Takes a GitHub or YouTrack issue for the Exposed project through reproduction, a failing test, a fix, validation and a pull request.
Runs issue triage and PR triage in parallel, then cross-analyzes the results to flag duplicate coverage, security gaps, P0 issues with no PR, and PR conflicts.
SKILL.md written in French; this summary is our English description.
Install RTK Combined Issue and PR Triage
$ npx skills add rtk-ai/rtk --skill rtk-triage -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rtk-ai/rtk rtk-triage --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/rtk-ai/rtk.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/rtk-triage .claude/skills/rtk-triage && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "rtk-triage" agent skill from https://github.com/rtk-ai/rtk/tree/develop/.claude/skills/rtk-triage into .claude/skills/rtk-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rtk-triage", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/rtk-ai/rtk/tree/develop/.claude/skills/rtk-triageType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add rtk-ai/rtk --skill rtk-triage -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rtk-ai/rtk rtk-triage --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rtk-ai/rtk.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/rtk-triage .agents/skills/rtk-triage && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "rtk-triage" agent skill from https://github.com/rtk-ai/rtk/tree/develop/.claude/skills/rtk-triage into .agents/skills/rtk-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rtk-triage", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rtk-ai/rtk --skill rtk-triage -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rtk-ai/rtk rtk-triage --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rtk-ai/rtk.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/rtk-triage .cursor/skills/rtk-triage && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "rtk-triage" agent skill from https://github.com/rtk-ai/rtk/tree/develop/.claude/skills/rtk-triage into .cursor/skills/rtk-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rtk-triage", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/rtk-ai/rtk.git --path .claude/skills/rtk-triage--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add rtk-ai/rtk --skill rtk-triage -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rtk-ai/rtk rtk-triage --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rtk-ai/rtk.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/rtk-triage .gemini/skills/rtk-triage && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "rtk-triage" agent skill from https://github.com/rtk-ai/rtk/tree/develop/.claude/skills/rtk-triage into .gemini/skills/rtk-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rtk-triage", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install rtk-ai/rtk rtk-triageInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add rtk-ai/rtk --skill rtk-triage -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/rtk-ai/rtk.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/rtk-triage .github/skills/rtk-triage && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "rtk-triage" agent skill from https://github.com/rtk-ai/rtk/tree/develop/.claude/skills/rtk-triage into .github/skills/rtk-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rtk-triage", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rtk-ai/rtk --skill rtk-triage -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install rtk-ai/rtk rtk-triage --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rtk-ai/rtk.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/rtk-triage .opencode/skills/rtk-triage && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "rtk-triage" agent skill from https://github.com/rtk-ai/rtk/tree/develop/.claude/skills/rtk-triage into .opencode/skills/rtk-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rtk-triage", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
rtk-triage- GitHub stars
- 83k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 485 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Runs issue triage and PR triage in parallel, then cross-analyzes the results to flag duplicate coverage, security gaps, P0 issues with no PR, and PR conflicts.
- Works in 5 steps: Préconditions → Data gathering (parallèle) → Triage individuel → …
- Running a weekly combined triage before sprint planning
- SKILL.md covers Quand utiliser, Workflow en 4 phases, Format du fichier sauvegardé and Règles
- Calls gh and git
What it does
This skill orchestrates two existing triage skills - one for issues, one for pull requests - running their data collection in parallel before combining the results into a cross-analysis that neither produces alone. After confirming the repository and the current date, it gathers up to 150 open issues and up to 200 open pull requests with their full metadata via the `gh` CLI, then runs the same categorization each individual skill would: issue type, risk color, staleness over 30 days, a mapping from issue number to referencing PR numbers, PR size, CI status, internal-versus-external authorship, file-overlap conflicts, and author clusters of three or more PRs.
The cross-analysis is where this skill adds value beyond the two individual ones: for any issue linked to two or more PRs, it builds a table comparing them and recommends a verdict - prefer the smaller PR at equal scope, prefer clean CI over dirty CI, prefer an internal PR over an external one, and flag file overlap above 80% as a near-certain conflict. It also checks for security-labeled issues with no linked PR at all, among other cross-checks.
Results are saved to a dated Markdown report under a fixed project-docs folder, and the skill accepts a language argument - French by default, or English - plus a flag to force saving the report even when it otherwise wouldn't.
When your agent uses it
- Running a weekly combined triage before sprint planning
- Finding duplicate PRs covering the same issue before reviewing
- Catching a security issue that has no linked pull request
Example prompts
- “Run the full RTK triage in English and save the report.”
- “Check if any of our open issues have two competing PRs.”
- “Find security issues that don't have a PR linked yet.”
Requirements
- git
- gh CLI authenticated against the repository
- Pre-approved tools (allowed-tools): Bash, Write, Read, AskUserQuestion
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit e4f0509. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
BashWriteReadAskUserQuestion
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
ghgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
RTK Combined Issue and PR Triage loads about 1.6k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 485 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Bash, Write, Read, AskUserQuestion
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from rtk-ai/rtk at commit e4f0509, republished under its Apache-2.0 licence (© rtk-ai). 485 words, ~1,622 tokens.
Download SKILL.mdSave it as
.claude/skills/rtk-triage/SKILL.md (or your agent's skills folder).- name
- rtk-triage
- description
- Triage complet RTK : exécute issue-triage + pr-triage en parallèle, puis croise les données pour détecter doubles couvertures, trous sécurité, P0 sans PR, et conflits internes. Sauvegarde dans claudedocs/RTK-YYYY-MM-DD.md. Args: "en"/"fr" pour la langue (défaut: fr), "save" pour forcer la sauvegarde.
- allowed-tools
- Bash, Write, Read, AskUserQuestion
- effort
- high
- tags
- triage, orchestration, issues, pr, security, cross-analysis, rtk
/rtk-triage
Orchestrateur de triage RTK. Fusionne issue-triage + pr-triage et produit une analyse croisée.
Quand utiliser
- Hebdomadaire ou avant chaque sprint
- Quand le backlog PR/issues grossit rapidement
- Pour identifier les doublons avant de reviewer
Workflow en 4 phases
Phase 0 — Préconditions
git rev-parse --is-inside-work-tree
gh auth statusVérifier que la date actuelle est connue (utiliser date +%Y-%m-%d).
Phase 1 — Data gathering (parallèle)
Lancer les deux collectes simultanément :
Issues :
gh repo view --json nameWithOwner -q .nameWithOwner
gh issue list --state open --limit 150 \
--json number,title,author,createdAt,updatedAt,labels,assignees,body
gh issue list --state closed --limit 20 \
--json number,title,labels,closedAt
gh api "repos/{owner}/{repo}/collaborators" --jq '.[].login'PRs :
# Fetcher toutes les PRs ouvertes — paginer si nécessaire (gh limite à 200 par appel)
gh pr list --state open --limit 200 \
--json number,title,author,createdAt,updatedAt,additions,deletions,changedFiles,isDraft,mergeable,reviewDecision,statusCheckRollup,body
# Si le repo a >200 PRs ouvertes, relancer avec --search pour paginer :
# gh pr list --state open --limit 200 --search "is:pr is:open sort:updated-desc" ...
# Pour chaque PR, récupérer les fichiers modifiés (nécessaire pour overlap detection)
# Prioriser les PRs candidates (même domaine, même auteur)
gh pr view {num} --json files --jq '[.files[].path] | join(",")'Phase 2 — Triage individuel
Exécuter les analyses de /issue-triage et /pr-triage séparément (même logique que les skills individuels) pour produire :
Issues :
- Catégorisation (Bug/Feature/Enhancement/Question/Duplicate)
- Risque (Rouge/Jaune/Vert)
- Staleness (>30j)
- Map
issue_number → [PR numbers]via scanfixes #N,closes #N,resolves #N
PRs :
- Taille (XS/S/M/L/XL)
- CI status (clean/dirty)
- Nos PRs vs externes
- Overlaps (>50% fichiers communs entre 2 PRs)
- Clusters (auteur avec 3+ PRs)
Afficher les tableaux standards de chaque skill (voir SKILL.md de issue-triage et pr-triage pour le format exact).
Phase 3 — Analyse croisée (cœur de ce skill)
C'est ici que ce skill apporte de la valeur au-delà des deux skills individuels.
3.1 Double couverture — 2 PRs pour 1 issue
Pour chaque issue liée à ≥2 PRs (via scan des bodies + overlap fichiers) :
| Issue | PR1 (infos) | PR2 (infos) | Verdict recommandé |
|---|---|---|---|
| #N (titre) | PR#X — auteur, taille, CI | PR#Y — auteur, taille, CI | Garder la plus ciblée. Fermer/coordonner l'autre |
Règle de verdict :
- Préférer la plus petite (XS < S < M) si même scope
- Préférer CI clean sur CI dirty
- Préférer "nos PRs" si l'une est interne
- Si overlap de fichiers >80% → conflit quasi-certain, signaler
3.2 Trous de couverture sécurité
Pour chaque issue rouge (#640-type security review) :
- Lister les sous-findings mentionnés dans le body
- Croiser avec les PRs existantes (mots-clés dans titre/body)
- Identifier les findings sans PR
Format :
## Issue #N — security review (finding par finding)
| Finding | PR associée | Status |
|---------|-------------|--------|
| Description finding 1 | PR#X | En review |
| **Description finding critique** | **AUCUNE** | ⚠️ Trou |Show full SKILL.md (212 more words)Show less
3.3 P0/P1 bugs sans PR
Issues labelisées P0 ou P1 (ou mots-clés : "crash", "truncat", "cap", "hardcoded") sans aucune PR liée.
Format :
## Bugs critiques sans PR
| Issue | Titre | Pattern commun | Effort estimé |
|-------|-------|----------------|---------------|Chercher un pattern commun (ex: "cap hardcodé", "exit code perdu") — si 3+ bugs partagent un pattern, suggérer un sprint groupé.
3.4 Nos PRs dirty — causes probables
Pour chaque PR interne avec CI dirty ou CONFLICTING :
- Vérifier si un autre PR touche les mêmes fichiers
- Vérifier si un merge récent sur develop peut expliquer le conflit
- Recommander : rebase, fermeture, ou attente
Format :
## Nos PRs dirty
| PR | Issue(s) | Cause probable | Action |
|----|----------|----------------|--------|3.5 PRs sans issue trackée
PRs internes sans fixes #N dans le body — signaler pour traçabilité.
Phase 4 — Output final
Afficher l'analyse croisée complète (sections 3.1 → 3.5)
Puis afficher le résumé chiffré :
## Résumé chiffré — YYYY-MM-DD
| Catégorie | Count |
|-----------|-------|
| PRs prêtes à merger (nos) | N |
| Quick wins externes | N |
| Double couverture (conflicts) | N paires |
| P0/P1 bugs sans PR | N |
| Security findings sans PR | N |
| Nos PRs dirty à rebaser | N |
| PRs à fermer (recommandé) | N |Sauvegarder dans claudedocs
date +%Y-%m-%d # Pour construire le nom de fichierSauvegarder dans claudedocs/RTK-YYYY-MM-DD.md avec :
- Les tableaux de triage issues + PRs (Phase 2)
- L'analyse croisée complète (Phase 3)
- Le résumé chiffré
Confirmer : Sauvegardé dans claudedocs/RTK-YYYY-MM-DD.md
Format du fichier sauvegardé
# RTK Triage — YYYY-MM-DD
Croisement issues × PRs. {N} PRs ouvertes, {N} issues ouvertes.
---
## 1. Double couverture
...
## 2. Trous sécurité
...
## 3. P0/P1 sans PR
...
## 4. Nos PRs dirty
...
## 5. Nos PRs prêtes à merger
...
## 6. Quick wins externes
...
## 7. Actions prioritaires
(liste ordonnée par impact/urgence)
---
## Résumé chiffré
...Règles
- Langue : argument
en/fr. Défaut :fr. Les commentaires GitHub restent toujours en anglais. - Ne jamais poster de commentaires GitHub sans validation utilisateur (AskUserQuestion).
- Si >200 issues ou >200 PRs : prévenir l'utilisateur et paginer (relancer avec
--searchough apiavec pagination). - L'analyse croisée (Phase 3) est toujours exécutée — c'est la valeur ajoutée de ce skill.
- Le fichier claudedocs est sauvegardé automatiquement sauf si l'utilisateur dit "no save".
© rtk-ai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/rtk-triage of rtk-ai/rtk.
Open the folder on GitHubat commit e4f0509
Compare with similar skills
RTK Combined Issue and PR Triage next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| RTK Combined Issue and PR Triage this skillrtk-ai/rtk | 83k | — | ~1.6k | Automated safety check: Notes | Apache-2.0 | |
| Exposed Bug Fix WorkflowJetBrains/Exposed | 9.3k | — | ~3.8k | Automated safety check: Pass | Apache-2.0 | |
| Pre-Release PR Triagejamiepine/voicebox | 57k | — | ~3.1k | Automated safety check: Pass | MIT | |
| Review Triage Phaseprisma/orm | 48k | — | ~995 | Automated safety check: Pass | Apache-2.0 | |
| Pre-Ship Review and Triagetw93/Waza | 7.2k | — | ~6.9k | Automated safety check: Pass | MIT | |
| Skills CLI PR Labelingvercel-labs/skills | 33k | — | ~310 | Automated safety check: Pass | MIT |
Similar skills
- Official
Pre-Release PR Triage
jamiepine/voicebox
Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.
- Official
Review Triage Phase
prisma/orm
Runs the triage step of the review-framework loop: reads fetched PR review state, builds `review-actions.json`, validates it and renders `review-actions.md`.
Pre-Ship Review and Triage
tw93/Waza
Reviews diffs and pull requests, triages issues, and checks release readiness, reporting findings with evidence and making no edits unless authorized.
- Official
Skills CLI PR Labeling
vercel-labs/skills
Labels a pull request in the skills CLI repo as bug, documentation or enhancement based on its description and patch, leaving existing labels untouched.
Ouroboros Maintainer Triage
Q00/ouroboros
Triages and works through GitHub issues and pull requests in the Q00/ouroboros repo as a maintainer, within a stated review boundary and clear limits on what it may change.
More from rtk-ai/rtk
Rust TDD Workflow
rtk-ai/rtk
Enforces red-green-refactor for Rust work, with idiomatic test patterns, a naming convention and a pre-commit gate of cargo fmt, clippy and test.
RTK Rust Design Patterns
rtk-ai/rtk
Describes seven Rust design patterns for the RTK CLI filter modules, with when to use each, RTK examples, and notes on when a pattern is overkill.
RTK Filter TDD in Rust
rtk-ai/rtk
Enforces red-green-refactor for new RTK output filters in Rust, using real captured fixtures, snapshot tests with insta and token-savings assertions.
RTK Rust Code Simplifier
rtk-ai/rtk
Reviews RTK's Rust code for over-engineering and verbose patterns, applying idioms like iterator chains and early returns while protecting a specific list of constraints from being simplified away.
RTK Issue Triage
rtk-ai/rtk
Audits open GitHub issues, categorizes them, flags duplicates and linked PRs in three phases, with optional deep analysis and comments posted only after validation.
PR Triage
rtk-ai/rtk
Audits a repository's open pull requests, deep-reviews chosen ones and drafts review comments that are only posted after you approve them.
Related
Categories
Questions about RTK Combined Issue and PR Triage
What does RTK Combined Issue and PR Triage do?
Runs issue triage and PR triage in parallel, then cross-analyzes the results to flag duplicate coverage, security gaps, P0 issues with no PR, and PR conflicts. This skill orchestrates two existing triage skills - one for issues, one for pull requests - running their data collection in parallel before combining the results into a cross-analysis that neither produces alone. After confirming the repository and the current date, it gathers up to 150 open issues and up to 200 open pull requests with their full metadata via the `gh` CLI, then runs the same categorization each individual skill would: issue type, risk color, staleness over 30 days, a mapping from issue number to referencing PR numbers, PR size, CI status, internal-versus-external authorship, file-overlap conflicts, and author clusters of three or more PRs.
When should I use RTK Combined Issue and PR Triage?
RTK Combined Issue and PR Triage fits situations like: running a weekly combined triage before sprint planning; finding duplicate PRs covering the same issue before reviewing; catching a security issue that has no linked pull request.
How do I install RTK Combined Issue and PR Triage in Claude Code?
Run `npx skills add rtk-ai/rtk --skill rtk-triage -a claude-code`. Or copy the skill folder (.claude/skills/rtk-triage in rtk-ai/rtk) into .claude/skills/rtk-triage in your project. Claude Code loads it when a task matches its description.
How do I install RTK Combined Issue and PR Triage in Codex?
Run `npx skills add rtk-ai/rtk --skill rtk-triage -a codex`. Or copy the skill folder (.claude/skills/rtk-triage in rtk-ai/rtk) into .agents/skills/rtk-triage in your project. Codex loads it when a task matches its description.
Can I use RTK Combined Issue and PR Triage in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rtk-ai/rtk --skill rtk-triage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rtk-triage, .gemini/skills/rtk-triage, .github/skills/rtk-triage and .opencode/skills/rtk-triage in your project.
What does RTK Combined Issue and PR Triage need to run?
Going by SKILL.md and its folder, RTK Combined Issue and PR Triage needs the command-line tools its instructions call (gh and git). Our summary lists: git; gh CLI authenticated against the repository. Its frontmatter pre-approves these tools: Bash, Write, Read, AskUserQuestion.
Does RTK Combined Issue and PR Triage access the network?
SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is RTK Combined Issue and PR Triage safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does RTK Combined Issue and PR Triage use?
RTK Combined Issue and PR Triage is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does RTK Combined Issue and PR Triage use?
About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to RTK Combined Issue and PR Triage?
Skills that share tags, products or a category with RTK Combined Issue and PR Triage: Exposed Bug Fix Workflow (JetBrains/Exposed, 9.3k stars), Pre-Release PR Triage (jamiepine/voicebox, 57k stars), Review Triage Phase (prisma/orm, 48k stars) and Pre-Ship Review and Triage (tw93/Waza, 7.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains RTK Combined Issue and PR Triage?
rtk-ai (a GitHub organization) maintains it in rtk-ai/rtk, which has 82,728 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 8, 2026.
Source: rtk-ai/rtk on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.