Plugins
1 pluginResults for “review-triage”
10 skillsTriage
Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
1 · bundle
Github Ops
Manage GitHub repositories: triage issues, review PRs, debug CI/CD, prepare releases, and monitor security alerts using the gh CLI.
226k
Inbox
Triage and review open GitHub issues and PRs against project contribution templates, producing a compliance report and optionally labeling, commenting, or closing items.
1 · bundle
More results
Github Ops
Manage GitHub repositories via the gh CLI: triage issues, review PRs, debug CI failures, create releases, and monitor security alerts.
1
Copilot Pr Autopilot
Automates repeated rounds of Copilot code review on GitHub pull requests: triggers review, triages threads, dispatches parallel fix agents, commits, replies, and loops until convergence.
36.2k · bundle
Arch Linux Triage
Diagnose and resolve Arch Linux issues using pacman, systemd, and rolling-release best practices.
36.2k
Social Science Literature Triage
Use for the search-planning stage of a literature review, when database lanes and language layers must be chosen, when DOI coverage policy is unclear, or when inclusion and exclusion criteria need drafting before any source is read; not for running the screening and PRISMA pipeline of a formal review, which is prisma-scoping-review-pipeline.
2
Github Ops
GitHub repository operations, automation, and management. Issue triage, PR management, CI/CD operations, release management, and security monitoring using the gh CLI. Use when the user wants to manage GitHub issues, PRs, CI status, releases, contributors, stale items, or any GitHub operational task beyond simple git commands.
2
Github Ops
Manages GitHub repositories via the gh CLI: triaging issues, reviewing PRs, debugging CI failures, preparing releases, and monitoring security alerts.
0
QA Methodology
Design and apply QA methodology for software teams: test strategy, regression testing, CI failure triage, test automation, quality gates and metrics, risk-based testing, exploratory testing, test design techniques, AI code quality gates (independent verification, acceptance-criteria testability review for agentic Spec-Driven Development), mutation-guided test hardening and review evidence (surviving mutants, weak assertions, diff-aware mutation testing), agentic eval design (dataset test design, judge-as-system-under-test, flaky-eval discipline), QA career levels (Senior/Staff/Principal), and SDET engineering (test infrastructure, gTAA, CI/CD integration). Do not use for root-cause debugging of production incidents, security implementation or threat modeling, or evaluation framework governance and statistical analysis — route those to systematic-debugging, secure-software-engineering, and agent-evals-and-observability respectively.
28 · bundle