Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Triage GitHub PRs and issues using vision-based scoring. Use when a user wants to prioritize, score, review, de-duplicate, or batch-process open pull request...
Triage GitHub PRs and issues using vision-based scoring. Use when a user wants to prioritize, score, review, de-duplicate, or batch-process open pull request...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Score and prioritize GitHub PRs against a project's vision document. Three-step workflow: onboard, scan, report.
# 1. Onboard: gather repo context, interview the owner python3 scripts/onboard.py https://github.com/owner/repo --output-dir ./triage-config # 2. Scan: score open PRs against the vision python3 scripts/scan.py https://github.com/owner/repo ./triage-config/vision.md --output scores.json # 3. Report: generate markdown triage reports python3 scripts/report.py scores.json --output-dir ./triage-reports
Run scripts/onboard.py with a GitHub repo URL. It fetches the README, CONTRIBUTING.md, recent releases, and repo metadata via gh CLI, then outputs an interview prompt. Use the interview prompt to ask the repo owner these questions: Identity & Mission: In one sentence, what is this project and who is it for? What problem does it solve that alternatives do not? What are your 3-5 non-negotiable principles? Priorities: 4. Rank contribution areas by importance: security, bugs, features, performance, docs, tests, refactoring 5. What types of PRs would you auto-reject? 6. What types of PRs would you fast-track? Red/Green Flags: 7. What patterns signal low-quality contributions? 8. What makes you excited to review a PR? 9. Specific areas where you want help? Context: 10. Growth mode, maintenance mode, or transitioning? 11. Upcoming milestones affecting prioritization? 12. How do you handle breaking changes? After the interview, generate two files in the output directory: vision.md - Project mission, identity, priorities, alignment signals rubric.md - Scoring rubric customized from references/rubric-template.md
Run scripts/scan.py with the repo URL and vision doc path. It: Fetches open PRs via gh pr list (title, body, labels, stats, author, date) Applies rule-based scoring: base 50, with positive/negative modifiers Detects potential duplicates via title similarity Outputs JSON with scores, reasoning, and distribution The scan uses heuristic scoring (keyword matching, diff size, test mentions). For deeper analysis, read the JSON output and apply additional LLM reasoning to ambiguous PRs (scores 40-60). Options: --count N - Number of PRs to fetch (default: 100) --output file.json - Save to file instead of stdout
Run scripts/report.py with the scan JSON. It generates four markdown files: prioritize.md - PRs scoring 80+ (fast-track for review) review.md - PRs scoring 50-79 (standard queue) close.md - PRs scoring below 50 (likely close or request changes) summary.md - Distribution, top 3, patterns, duplicates, active authors
Base score: 50. Key modifiers: SignalPointsSecurity fix+20Bug fix with tests+10Core functionality improvement+10Performance (measured)+8Small focused diff+5Has tests+5Spam/promotion-30Unwanted dependency-25Large diff, no tests-15No description-5 Full rubric: references/rubric-template.md Example vision doc: references/example-vision.md
Set up a cron job to scan weekly: description: Weekly PR triage for owner/repo schedule: "0 9 * * MON" model: anthropic/claude-sonnet-4-20250514 channel: telegram Cron prompt: "Run pr-triage scan on https://github.com/owner/repo using ./triage-config/vision.md, generate reports, and send the summary."
gh CLI installed and authenticated (gh auth login) Python 3.10+ No additional Python packages needed (stdlib only)
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.