Forgent skills

skill: pr-triage version: "1.0.0" context: consumes: [pr_url] produces: [triage_report] memory: short-term strategy: tools: [bash] approach: gate-check effort: light steps: - fetch PR metadata and diff via gh - check if PR is closed, draft, automated, or already reviewed - if eligible, summarize the nature of changes (files changed, purpose, risk areas) - return eligibility status with reason and structured summary guardrails:

• timeout: 2min
• fail_closed
• max_summary_length: 500 observability: trace_level: minimal metrics: [tokens, latency] security: filesystem: none network: allowlist secrets: [GITHUB_TOKEN] negotiation: file_conflicts: yield priority: 1 when_to_use: triggers:
  • before any automated code review
  • when a PR URL is provided for review dont_use:
  • for manual reviews without a PR
  • for local-only code review anti_patterns:
• excuse: "Skipping eligibility check" reality: "Reviewing closed/draft/automated PRs wastes tokens and creates noise"