OpenParable
Skip to content
← Back to skills

PR Issue Triage

Productivity
pr-issue-triage

PR Issue Triage is an Agent Skill for productivity published in the mkurman/zorai repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Canonical PR/Issue triage pack combining repo review queues with work tracker context and approval-gated write-backs.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/mkurman/zorai/blob/HEAD/skills/workflow-packs/pr-issue-triage/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/pr-issue-triage, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

PR / Issue Triage

User story

I want one triage view across repo review items and issue tracker work, so I can see stale, blocked, and actionable items without manually stitching together GitHub/GitLab and Linear/Jira.

Pack contract

Prerequisites and readiness

  • Requires one repo connector: github or gitlab
  • Optionally enriches with one tracker connector: linear or jira
  • If the tracker is unavailable, the pack still runs as repo-only triage and clearly marks tracker enrichment as degraded.

Inputs and configuration fields

  • repo_connector: github or gitlab
  • tracker_connector: linear, jira, or none
  • owner / repo or equivalent project coordinates
  • include_writeback_suggestions: boolean
  • stale_days: integer threshold

Outputs and delivery targets

  • merged queue showing:
    • open PRs / review items
    • open issues / work items
    • stale items
    • blocked items
    • suggested next actions
  • source links should point back to the original PR/issue/tracker item
  • write-back suggestions must be clearly marked approval-required

Manual run recipe

  1. List repo review items and work items from the chosen repo connector.
  2. If tracker is ready, fetch tracker work items and merge by title/ID/reference where possible.
  3. Summarize stale and blocked items.
  4. Suggest write-backs separately from the read-only report.

Example routine wiring

Schedule as a weekday triage routine or on-demand review block. Example payload description:

Run the canonical PR/Issue Triage pack for the main repo, merge repo/tracker context, and surface approval-gated write-back suggestions.

Example prompt

Run PR/Issue Triage for owner/repo using GitHub plus Linear. Show stale PRs, blocked issues, and suggested labels/comments, but do not perform write-backs without approval.

Failure and recovery behavior

  • Missing repo connector -> fail closed with setup hint.
  • Missing tracker connector -> continue with repo-only triage.
  • Proposed write-back with no approval -> keep suggestion in the report, do not execute it.

Verification checklist

  • Manual repo-only proof passes.
  • Manual repo + tracker proof passes.
  • Missing tracker degrades gracefully.
  • Write-back suggestions are clearly approval-gated.
  • Source links are present for triaged items.