Results for “request-triage”

Triage GitHub issues through a label-based state machine. 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.

Triage and review open GitHub issues and PRs against project contribution templates, producing a compliance report and optionally labeling, commenting, or closing items.

Classify, prioritize, and route incoming support tickets by extracting intent and entities, assigning severity, and generating initial responses. Use when the user requests ticket triage or provides relevant inputs for this workflow.

Manage GitHub repositories via the gh CLI: triage issues, review PRs, debug CI failures, create releases, and monitor security alerts.

Coordinates GitHub and Linear by triaging issues and pull requests, linking active work, and keeping GitHub public-facing while Linear tracks internal execution.

Operate execution flow across GitHub and Linear by triaging issues and pull requests, linking active work, and keeping GitHub public-facing while Linear remains the internal execution layer.

Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.

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.

Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.

Moves issues and external PRs through a state machine of triage roles — categorise, verify, grill, and write agent-ready briefs. Use when the user says "triage this issue" or wants agent-ready issue briefs.

Runs recurring inbox triage by classifying recent emails, researching new senders, generating recommendations, and drafting replies (never sends).

Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.

Interactive triage of the approval gate. Walks each block in inbox/tasks_pending.md and routes it — approve / reject / attach-as-follow-up / edit / skip. See workflows/task_tracking.md for the why.

Triage and categorize findings for the CLI todo system

Triage issues through a state machine driven by triage roles, including gathering context, recommending actions, and applying outcomes.

Triage customer support tickets/emails/chats into categories, priority, and next action; draft responses and create reproducible steps; use for Zendesk/Intercom/Help Scout exports or pasted threads.

Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.

Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.

Triage a bug or issue by exploring the codebase to find root cause, then create a GitHub issue with a TDD-based fix plan. Use when user reports a bug, wants to file an issue, mentions "triage", or wants to investigate and plan a fix for a problem.

Sorts an email inbox into reply-now, reply-later, and ignore buckets, and drafts replies for urgent messages using an existing Gmail connector.

Triage web application vulnerability findings from DAST/SAST scanners using OWASP risk rating methodology to separate true positives from false positives and prioritize remediation.

Triages security incidents by classifying type, assigning severity based on business impact, enriching with threat intelligence, and routing to appropriate response teams using NIST SP 800-61r3 and SANS PICERL frameworks.

Fetches and summarizes TestFlight crash reports, beta feedback, and performance diagnostics using the asc CLI.

Triage a raw, vague issue or bug report into a structured document that names what is known, what is missing, and what to do next. Use when an incoming issue, bug report, or problem description is too vague or incomplete for investigation or planning, and recommend the right next han skill. Does not investigate root causes or trace code paths — use investigate for debugging, diagnosis, and root cause analysis. Does not plan features or build solutions — use plan-a-feature or plan-implementation for that.

Use when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a structured JSON report to guide workflows and guardrails.

You are a data triager that answers data questions by routing them across a network of skills and agents. These questions may involve pulling data from a Snowflake warehouse, computing metrics, locating relevant tables or fields, diagnosing a metric change, or performing exploratory analysis. Your job is to determine how to answer a question and which skills and subagents to invoke.

Moves tracker issues through a structured triage state machine with category and readiness decisions; use to evaluate or prepare work items for implementation.

Triage and orient GitHub repository, pull request, and issue work through the connected GitHub app. Use when the user asks for general GitHub help, wants PR or issue summaries, or needs repository context before choosing a more specific GitHub workflow.

Triage Linear or Jira backlogs and run bug sweeps via the Composio CLI. Bulk-fetch issues, deduplicate, relabel, reassign, and post summaries all from the shell.

Decode an incoming message into a structured breakdown that separates the literal ask from the job-to-be-done, before replying to a loaded Slack ping, email, mandate, or escalation.