enclawed-pr-maintainer

Triage Enclawed pull requests with evidence-backed validation and label handling.

2|Updated May 23, 2026
One-click install
npx skills add https://github.com/enclawed/enclawed-oss --skill enclawed-pr-maintainer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: enclawed-pr-maintainer
Source: https://github.com/enclawed/enclawed-oss/tree/main/.agents/skills/enclawed-pr-maintainer
Command: npx skills add https://github.com/enclawed/enclawed-oss --skill enclawed-pr-maintainer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintainers make safe, consistent decisions on Enclawed pull requests and related issues, reducing guesswork when validating fixes, applying labels, or deciding whether to merge or close.

Core Features & Use Cases

  • Bug-Fix Validation: Check that a claimed fix has real repro evidence, a verified root cause, and a change that touches the implicated code path.
  • Issue and PR Triage: Search broadly for related discussions, then apply the right close or triage label when a submission matches an established auto-close reason.
  • Safe GitHub Communication: Draft comments and landing notes without shell-escaping mistakes or broken multiline formatting.
  • Review Follow-Up: Resolve bot conversations, verify remaining concerns, and keep review threads tidy before landing.
  • Use Case: When a pull request claims to fix a regression, use this Skill to verify the evidence, recommend the correct label or review action, and prepare a safe maintainer response.

Quick Start

Ask for a maintainer-style review of the pull request with evidence checks, label guidance, and a safe comment draft if follow-up is needed.

Frequently Asked Questions about enclawed-pr-maintainer

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

FAQPage Schema
How do I validate a GitHub pull request that claims to fix a bug?

To validate a GitHub pull request for a bug fix, check for real repro evidence, verify the root cause, and ensure the code changes touch the implicated code path before approving the merge.

What's the best way to triage pull requests and apply labels for auto-closure?

The best way to triage pull requests is to search broadly across titles, bodies, and comments for related discussions, then apply the correct auto-close label when a submission matches an established reason.

How do I safely draft and format multiline GitHub review comments?

To safely draft GitHub review comments, generate landing notes and responses that avoid shell-escaping mistakes and prevent broken multiline formatting during the review follow-up process.

Can I resolve bot review threads and verify remaining concerns before landing a PR?

Yes, you can resolve bot review conversations, verify any remaining concerns, and keep review threads tidy before landing a pull request to ensure strict maintainer-level hygiene.

When do I need to apply maintainer rigor to a pull request landing decision?

You need to apply maintainer rigor when deciding whether to merge or close a pull request, ensuring evidence-backed verification and correct auto-close label handling are completed beforehand.

Why does my pull request triage miss related issues and discussions on GitHub?

Your pull request triage may miss related issues if your search is too narrow; you must search broadly across issue and PR titles, bodies, and comments to find all relevant discussions.