godseye-pr-maintainer

Automate triage, labeling, and safe decision-making for Gods Eye PRs and issues.

4|2|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/bitan-del/gods-eye --skill godseye-pr-maintainer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: godseye-pr-maintainer
Source: https://github.com/bitan-del/gods-eye/tree/main/.agents/skills/godseye-pr-maintainer
Command: npx skills add https://github.com/bitan-del/gods-eye --skill godseye-pr-maintainer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates maintainer triage, labeling, and safe decision-making for Gods Eye PRs and issues.

Core Features & Use Cases

  • Apply correct close and triage labels to issues and PRs based on predefined rules.
  • Enforce the bug-fix evidence bar by requiring root cause, tests, and verifiable fixes before landing.
  • Generate safe, actionable maintainer comments and coordinate follow-up checks across review threads.

Quick Start

Review a new PR or issue, apply the correct triage labels, and prepare a safe, evidenced-based decision for merge or closure.

Frequently Asked Questions about godseye-pr-maintainer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate pull request triage and labeling on GitHub?

Automate pull request triage by applying predefined close and triage labels to PRs and issues. The workflow searches for related items, enforces bug-fix evidence, and generates safe maintainer comments for reviewer-verified merges.

What is the best way to enforce bug-fix evidence requirements before merging a pull request?

Enforce bug-fix evidence requirements by demanding root cause analysis, regression checks, and verifiable tests before a PR lands. This safe decision-making flow ensures reviewer-verified merges and prevents untracked issues from entering the codebase.

Can I automatically generate maintainer comments for GitHub issues and PRs?

Generate safe, actionable maintainer comments automatically by coordinating follow-up checks across review threads. The workflow triages issues, applies labels, and prepares evidenced-based decisions for merge or closure directly in the repository.

How does PR triage automation handle related issue searches during code review?

PR triage automation searches for related issues and PRs during code review to provide context for safe decision-making. It applies appropriate triage labels and coordinates follow-up checks to guide the reviewer-verified landing flow.

Do I need specific GitHub repository rules to use automated PR triage for maintainer workflows?

Automated PR triage for maintainer workflows requires predefined close and triage label rules to function correctly. It operates within your GitHub repositories to enforce bug-fix evidence bars and guide safe, reviewer-verified pull request merges.