skills.rest
majunbao
majunbaoCOMMUNITY
Explore all skills by this author →
GitHub

openclaw-pr-maintainer

Triage OpenClaw PRs and issues with maintainer labels and closures.

Updated Dec 6, 2016
Search Tags:#automation#workflow#github#review#pr#triage#pull-request
One-click install
npx skills add https://github.com/majunbao/learn --skill openclaw-pr-maintainer-majunbao
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openclaw-pr-maintainer
Source: https://github.com/majunbao/learn/tree/main/openclaw_tags/openclaw-2026.4.24/.agents/skills/openclaw-pr-maintainer
Command: npx skills add https://github.com/majunbao/learn --skill openclaw-pr-maintainer-majunbao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines maintainer-oriented GitHub workflows by providing a disciplined approach to reviewing and closing PRs and issues with appropriate labels and evidence checks.

Core Features & Use Cases

  • Apply close and triage labels correctly based on auto-close reasons.
  • Enforce the bug-fix evidence bar before landing.
  • Follow safe GitHub text handling, search hygiene, and PR review standards.
  • Use standardized processes for maintaining project health across PRs and issues.

Quick Start

Review incoming PRs and apply the appropriate maintainer labels and closures according to the rules.

Frequently Asked Questions about openclaw-pr-maintainer

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

FAQPage Schema
How do I automate GitHub PR triage with maintainer evidence checks?▼

Automate GitHub PR triage by applying maintainer-focused labels, comments, and closures based on auto-close reasons. The workflow enforces evidence-based checks before landing PRs to ensure accurate and safe triage.

What is the best way to manage pull-request closures with proper labels?▼

Manage pull-request closures by applying triage labels and comments according to specific auto-close reasons. This standardized process enforces safe GitHub text handling and maintains project health across PRs and issues.

How does the bug-fix evidence bar work before landing a PR?▼

The bug-fix evidence bar works by requiring explicit evidence-based checks before a PR is landed. This safety constraint ensures that only validated changes merge while maintaining quality and consistency across the repository.

Does this GitHub review workflow support automated issue closures?▼

Yes, this GitHub review workflow supports automated issue closures by applying maintainer-focused labels and comments when auto-close reasons apply, following standardized search and hygiene practices for accurate triage.

What are the limitations of automated PR triage for maintainer workflows?▼

Automated PR triage limitations include strict adherence to safe GitHub text handling and explicit safety constraints. It operates within standardized processes to maintain quality, requiring valid auto-close reasons and evidence before action.

Related Skills

Explore More Software Engineering Skills→
mkikenmkiken
1

pr-create-by-branch

Generate GitHub Pull Request titles and bodies from branch diffs.

Community
Intermediate
ShmurdocShmurdoc

land-and-deploy

Merge pull requests, monitor CI pipelines, and verify production canary health.

Community
Advanced
Ramprasad4121Ramprasad4121
1

audit-prep-assistant

Prepare codebases for security review with static analysis and documentation.

Community
Advanced
openyakopenyak
704

ticket-triage

Categorize, prioritize, and route support tickets with P1-P4 priority.

Official
Advanced