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.